Testing VMware vCenter Driver with DevStack and getting Cinder Conversion Error

asked 2017-07-01 02:57:45 -0600

Hello All,

I'm testing the VMware vCenter Driver with DevStack Ocata on a CentOS 7.3 Virtual Machine, in order to be able to launch instances from the Horizon Dashboard and run them on a vShpere 5.5 Cluster.

Basically the Devstack setup seems to work fine, since I'm able to run a couple of small guests using Qemu driver (since I'm running in nested mode).

Following this guide for my Ocata version:

https://docs.openstack.org/ocata/config-reference/compute/hypervisor-vmware.html (https://docs.openstack.org/ocata/conf...)

when I add the VMware vCenter Driver config to nova.conf I can see that Nova-compute is able to connect to the vCenter server and from the Dashboard I can see the VMware Hypervisor with its resources.

Then if try to Launch an Instance starting from a pre-loaded VMDK image the Build fails with the following error:

Error: Build of instance 03061239-c470-4feb-bada-fdc2f946a92f aborted: Block Device Mapping is Invalid

and in the Cinder Log there are the following messages:

Jul  1 01:06:58 devstack01 cinder-volume: 2017-07-01 01:06:58.513 45003 ERROR cinder.volume.flows.manager.create_volume [req-8909e893-d5ae-403f-8363-07a590369c8a d65e6fb5db3a4060bb81d7ea0e71fa31 53acbb91ecf2487fb2bcff9a9f551755 - - -] Failed to copy image 0199ccc3-25d0-43e9-b0ea-409089a86524 to volume: b33a7c41-446a-4df7-8f15-17446db3a322: ProcessExecutionError: Unexpected error while running command.
Jul  1 01:06:58 devstack01 cinder-volume: Command: sudo cinder-rootwrap /etc/cinder/rootwrap.conf qemu-img convert -t none -f vmdk -O raw /opt/stack/data/cinder/conversion/tmp9whDdIdevstack01.mydomain.local@lvmdriver-1 /dev/mapper/stack--volumes--lvmdriver--1-volume--b33a7c41--446a--4df7--8f15--17446db3a322
Jul  1 01:06:58 devstack01 cinder-volume: Exit code: 1
Jul  1 01:06:58 devstack01 cinder-volume: Stdout: u''
Jul  1 01:06:58 devstack01 cinder-volume: Stderr: u"qemu-img: Could not open '/opt/stack/data/cinder/conversion/tmp9whDdIdevstack01.mydomain.local@lvmdriver-1': invalid VMDK image descriptor\n"

So it seems that Cinder is not aware of the VMware Driver Config and is trying to convert the image, which is a wrong action IMO.

From what I understand from the documentation, Cinder should not convert the image, but Glance should be able to deploy the Image to VCenter "as-is" in order to launch the instance on the vSphere CPU.

Any ideas on what is missing from my setup?

Thanks in advance!

Best regards,

Luca

edit retag flag offensive close merge delete