[Bug 1969643] [NEW] RBD: Unable to delete a volume which has snapshot/volume children

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

[Impact]
Deleting a volume will fail if it has snapshot or volume children, resulting in an ImageBusy error.

[Fix]
Upstream has a patch that uses RBD flatten operations to break dependencies between volumes and snapshots, reducing failures when using RBD volume clones and snapshots.

commit 1a675c9aa178c6d9c6ed10fd98f086c46d350d3f
Author:     Eric Harney <eharney at redhat.com>
CommitDate: Fri Dec 1 10:17:05 2023 -0500

    RBD: Flattening of child volumes during deletion

[Test Plan]
1. Prepare an OpenStack environment with cinder-ceph
2. Create a volume named "vol"
openstack volume create --image jammy --size 10 vol
3. Create a snapshot of the volume "vol"
openstack volume snapshot create --volume vol vol-snap
4. Create a volume named "vol-copy" from the snapshot
openstack volume create --snapshot vol-snap vol-copy
5. Delete the snapshot and then delete the volume "vol"
openstack volume snapshot delete vol-snap
openstack volume delete vol
6. Confirm that the volume "vol" is successfully deleted
openstack volume list

[Where problems could occur]
The patch primarily modifies the workflow for volume deletion when using RBD as the backend and adds a retry mechanism for unprotecting snapshots during snapshot deletion.
If the patch has any undiscovered issues, it will only affect volume deletion. Other functionalities or non-RBD backends will not be impacted.

** Affects: cinder
     Importance: Medium
     Assignee: Eric Harney (eharney)
         Status: Fix Released

** Affects: cinder (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: cinder (Ubuntu Jammy)
     Importance: Undecided
     Assignee: Chengen Du (chengendu)
         Status: In Progress


** Tags: drivers patch rbd
-- 
RBD: Unable to delete a volume which has snapshot/volume children
https://bugs.launchpad.net/bugs/1969643
You received this bug notification because you are a member of Ubuntu Sponsors, which is subscribed to the bug report.