DellEMC VNX: original volume can not be deleted on array backend if its snapshot has been used.
Bug #1794646 reported by
Sam Wan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Rajat Dhasmana |
Bug Description
Scenario to reproduce:
1. Create a vol (testvol)
2. Create a snapshot of the vol (testsnap)
3. Create a new vol from the snapshot (newvol)
4. Delete the new vol (newvol)
5. Delete snapshot (testsnap)
6. Delete the original vol (testvol)
The original volume has gone from cinder database ie: 'openstack volume list' can not see the original volume.
But it's still on array backend with a snapshot.
tags: | added: dellemc vnx |
Changed in cinder: | |
assignee: | nobody → Ryan Liang (ryan-liang) |
Changed in cinder: | |
assignee: | Ryan Liang (ryan-liang) → Rajat Dhasmana (whoami-rajat) |
To post a comment you must log in.
Async migration was used in the process of creating a volume from a snapshot and an internal temp snapshot was created for async migration.
The bug was caused by that the temp snapshot wasn't deleted. Then the LUN hosting the snapshot cannot be deleted from the VNX storage.