Actions
Bug #41841
closedmgr/volumes: missing protection for `fs volume rm` command
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Correctness/Safety
Target version:
% Done:
0%
Source:
Tags:
Backport:
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
Currently can remove a filesytem, its data and meta data pools, and MDSes with a `fs volume rm` ceph mgr command. Maybe add a protection such as '--yes-i-really-mean-it' flag requirement?
Updated by Ramana Raja over 4 years ago
- Subject changed from mgr/volumes: missing protection to `fs volume rm` command to mgr/volumes: missing protection for `fs volume rm` command
Updated by Jos Collin over 4 years ago
- Status changed from In Progress to Fix Under Review
Updated by Ramana Raja over 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 4 years ago
- Copied to Backport #42149: nautilus: mgr/volumes: missing protection for `fs volume rm` command added
Updated by Nathan Cutler over 4 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