Train vmdk driver doesn't copy data into vmdk from glance correctly

Bug #1914820 reported by Ryan Fuerst
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Cinder
New
Medium
Unassigned

Bug Description

Upgraded from OpenStack Stein (openstack-ansible deployment methods) to Train. The VMware vmdk driver when creating a volume from an Image doesn't copy any data over into the vmdk on the ESX side. Everything says things worked correctly, the volume gets created, openstack logs say its good but when you log into ESX the volume doesn't actually have any data in it and is 0 size. downgrade to stein it works correctly, train and above this doesn't work. And all cinder log files say it copied everything over successfully.

If you try to launch and Instance from this volume you get OS not found (because their is no data in the volume)

Tags: image stein vmdk
Revision history for this message
Ryan Fuerst (rfuerst42) wrote :
Revision history for this message
Ryan Fuerst (rfuerst42) wrote :
Revision history for this message
Ryan Fuerst (rfuerst42) wrote :

esx log files

Changed in cinder:
assignee: nobody → Zahid Hasan (akkim31)
status: New → Confirmed
status: Confirmed → Fix Released
information type: Public → Public Security
Eric Harney (eharney)
information type: Public Security → Public
Revision history for this message
Ryan Fuerst (rfuerst42) wrote :

I see this marked Fixed Release, what is the fix?

Ryan Fuerst (rfuerst42)
Changed in cinder:
status: Fix Released → New
Changed in cinder:
importance: Undecided → Medium
tags: added: vmdk
tags: added: image stein
Revision history for this message
Ryan Fuerst (rfuerst42) wrote :

This works in Stein, fails in Train and above

Revision history for this message
Ryan Fuerst (rfuerst42) wrote :

Line 1263 in the train version

                http_method='POST') <--- that seems to be the code change between stein & train causing this problem.

Revision history for this message
Ryan Fuerst (rfuerst42) wrote :

Commit

https://github.com/openstack/cinder/commit/748ab113d68260fecd0f978b8de0e6b5f62e38f5

Seems to be when this defect was introduced against normal Datastores (I do not have a VVOL to test against)

Revision history for this message
Xiangfei Zhu (xiangfeiz) wrote :

@Ryan, if you remove http_method='POST' or change POST to PUT, is creating a volume from image successful? I'm asking because you may have the env handy for a test.

Revision history for this message
Ryan Fuerst (rfuerst42) wrote :

If I remove that line then things work, haven't tried changing it to PUT. Currently I have a normal Datastore environment not one with a VVOL setup. Not sure when I'll be able to test if that change breaks when using VVOLS or not.

Revision history for this message
Ryan Fuerst (rfuerst42) wrote :

Tested a VVOL setup, same results, no data in the volume created in the datastore.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.