VMware: Detach after snapshot leaves volume in inconsistent state
Bug #1243222 reported by
Kartik Bommepally
This bug report is a duplicate of:
Bug #1252967: VMware: delete vm snapshot after nova snapshot.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Confirmed
|
High
|
Gary Kotton | ||
Bug Description
Steps:
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) |
| Changed in nova: | |
| status: | New → Confirmed |
| summary: |
- VMware: Detach leaves volume in inconsistent state + VMware: Detach after snapshot leaves volume in inconsistent state |
Revision history for this message
| Vui Lam (vui) wrote | #1 |
| Changed in nova: | |
| importance: | Undecided → High |
Revision history for this message
| Vui Lam (vui) wrote | #2 |
To post a comment you must log in.
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?