Project

General

Profile

Bug #45910

pybind/mgr/volumes: volume deletion not always removes the associated osd pools

Added by Kotresh Hiremath Ravishankar 4 months ago. Updated about 2 months 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:

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


Related issues

Copied to fs - Backport #46234: octopus: pybind/mgr/volumes: volume deletion not always removes the associated osd pools Resolved
Copied to fs - Backport #46235: nautilus: pybind/mgr/volumes: volume deletion not always removes the associated osd pools Resolved

History

#1 Updated by Kotresh Hiremath Ravishankar 4 months ago

  • Status changed from New to In Progress
  • Assignee set to Kotresh Hiremath Ravishankar

#2 Updated by Kotresh Hiremath Ravishankar 4 months ago

  • Status changed from In Progress to Fix Under Review
  • Assignee changed from Kotresh Hiremath Ravishankar to Greg Farnum
  • Severity deleted (3 - minor)
  • Pull request ID set to 35420

#3 Updated by Kotresh Hiremath Ravishankar 4 months ago

  • Assignee changed from Greg Farnum to Kotresh Hiremath Ravishankar
  • Severity set to 3 - minor

#4 Updated by Patrick Donnelly 3 months ago

  • Status changed from Fix Under Review to Pending Backport
  • Target version set to v16.0.0
  • Source set to Development

#5 Updated by Nathan Cutler 3 months ago

  • Copied to Backport #46234: octopus: pybind/mgr/volumes: volume deletion not always removes the associated osd pools added

#6 Updated by Nathan Cutler 3 months ago

  • Copied to Backport #46235: nautilus: pybind/mgr/volumes: volume deletion not always removes the associated osd pools added

#7 Updated by Nathan Cutler about 2 months 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".

Also available in: Atom PDF