VMware: Detach after snapshot leaves volume in inconsistent state

Bug #1243222 reported by Kartik Bommepally on 2013-10-22
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Gary Kotton

Bug Description

1. Create instance in nova
2. Create volume in cinder
3. Attach volume to instance
4. Create image from the instance (this snapshots the instance and volume disks)
5. Detach volume from instance

After this volume will point to a read only older version VMDK file and not the latest version VMDK after snapshot was done.

Changed in nova:
assignee: nobody → Gary Kotton (garyk)
Gary Kotton (garyk) on 2013-10-23
Changed in nova:
status: New → Confirmed
summary: - VMware: Detach leaves volume in inconsistent state
+ VMware: Detach after snapshot leaves volume in inconsistent state
Vui Lam (vui) wrote :

I was going to file a more general snapshot-related bug:

VMware driver's snapshot operation takes a snapshot, but does not delete it afterwards.

but then I saw this. I think deleting the vm's snapshot after nova snapshot is the right thing to do anyway, and it probably will help with this problem. Gary, do you want to give that a try?

Changed in nova:
importance: Undecided → High
Vui Lam (vui) wrote :

Kartik, I have associated the fix to delete the vm snapshot after the nova snapshot, which will have the side effect of restoring the volume disk chain. Do you still want to use this bug to track any other aspect of the reported problem.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers