Cinder VMDK driver : uuid of VMDK disk file needs to be the same as of corresponding Cinder volume ID
Bug #1475738 reported by
Sunitha K
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Wishlist
|
Vipin Balachandran |
Bug Description
When we create Cinder volume of VMDK type, the uuid of virtual disk is auto-generated. Because of this it's difficult for an end user to identify the Openstack Cinder created/attached volumes from within the guest OS.
Change proposed - use the uuid of Cinder volume as the uuid for Virtual disk as well when the shadow VM template is updated in Cinder VMDK driver.
Changed in cinder: | |
assignee: | nobody → Vipin Balachandran (vbala) |
Changed in cinder: | |
status: | Incomplete → Confirmed |
Changed in cinder: | |
milestone: | none → liberty-3 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | liberty-3 → 7.0.0 |
To post a comment you must log in.
To view the volume uuid inside the guest vm, the vmx file needed to be updated with disk.EnableUUID = True