Project

General

Profile

Actions

Bug #45662

closed

pybind/mgr/volumes: volume deletion should check mon_allow_pool_delete

Added by Patrick Donnelly almost 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
High
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.


Related issues 2 (0 open2 closed)

Copied to CephFS - Backport #46477: octopus: pybind/mgr/volumes: volume deletion should check mon_allow_pool_deleteResolvedKotresh Hiremath RavishankarActions
Copied to CephFS - Backport #46478: nautilus: pybind/mgr/volumes: volume deletion should check mon_allow_pool_deleteResolvedRamana RajaActions
Actions

Also available in: Atom PDF