Actions
Bug #45910
closedpybind/mgr/volumes: volume deletion not always removes the associated osd pools
Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
% Done:
0%
Source:
Development
Tags:
Backport:
octopus,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
mgr/volumes
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
The volume deletion doesn't remove the associated osd pools. The pools are removed only if the volume is created using mgr plugin and not if created with custom osd pools. This is because mgr plugin generates pool names with specific pattern. Both create and delete volume relies on it. The delete volume should not rely on pattern. It should discover the osd pools associated with volume before deletion. ##Create a vstart cluster #env MDS=3 ../src/vstart.sh -d -b -n --without-dashboard #cd build #bin/ceph osd pool create cephfs_data1 8 #bin/ceph fs add_data_pool a cephfs_data1 #bin/ceph fs volume rm a --yes-i-really-mean-it #bin/ceph osd pool ls device_health_metrics cephfs_data1
Actions