Actions
Bug #45662
closedpybind/mgr/volumes: volume deletion should check mon_allow_pool_delete
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
[ceph: root@li822-21 /]# ceph fs volume rm a Error EPERM: WARNING: this will *PERMANENTLY DESTROY* all data stored in the filesystem 'a'. If you are *ABSOLUTELY CERTAIN* that is what you want, re-issue the command followed by --yes-i-really-mean-it. [ceph: root@li822-21 /]# ceph fs volume rm a --yes-i-really-mean-it Error EPERM: pool deletion is disabled; you must first set the mon_allow_pool_delete config option to true before you can destroy a pool [ceph: root@li822-21 /]# ceph config set mon mon_allow_pool_delete true [ceph: root@li822-21 /]# ceph fs volume rm a --yes-i-really-mean-it Error ENOENT: Filesystem not found for volume 'a' [ceph: root@li822-21 /]# ceph osd pool ls device_health_metrics cephfs.a.meta cephfs.a.data
Either the plugin should check this config before proceeding with any destructive action or somehow override mon_allow_pool_delete.
Updated by Kotresh Hiremath Ravishankar almost 4 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 35361
Updated by Patrick Donnelly almost 4 years ago
- Status changed from Fix Under Review to Pending Backport
- Source set to Development
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46477: octopus: pybind/mgr/volumes: volume deletion should check mon_allow_pool_delete added
Updated by Nathan Cutler almost 4 years ago
- Copied to Backport #46478: nautilus: pybind/mgr/volumes: volume deletion should check mon_allow_pool_delete added
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions