Open Stack

Hi OpenStack Developers!

I'm using the trunk version of OpenStack and I have a multi node devstack installation without shared storage. I booted an instance from a volume and then I tried to live migrate it to another compute node but I got the following exception:

2013-10-03 16:49:25.908  [01;31mERROR nova.openstack.common.rpc.amqp [ [01;36mreq-959589d1-c66d-41f8-bc0c-e874b7622a80  [00;36madmin admin [01;31m]  [01;35m [01;31mException during message handling [00m
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00mTraceback (most recent call last):
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m  File "/opt/stack/nova/nova/openstack/common/rpc/amqp.py", line 461, in _process_data
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m    **args)
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m  File "/opt/stack/nova/nova/openstack/common/rpc/dispatcher.py", line 172, in dispatch
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m    result = getattr(proxyobj, method)(ctxt, **kwargs)
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m  File "/opt/stack/nova/nova/exception.py", line 90, in wrapped
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m    payload)
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m  File "/opt/stack/nova/nova/exception.py", line 73, in wrapped
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m    return f(self, context, *args, **kw)
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m  File "/opt/stack/nova/nova/compute/manager.py", line 4004, in pre_live_migration
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m    migrate_data)
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m  File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 4118, in pre_live_migration
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m    disk_info)
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m  File "/opt/stack/nova/nova/virt/libvirt/driver.py", line 4174, in _create_images_and_backing
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m    disk_info = jsonutils.loads(disk_info_json)
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m  File "/opt/stack/nova/nova/openstack/common/jsonutils.py", line 166, in loads
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m    return json.loads(s)
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m  File "/usr/lib/python2.7/json/__init__.py", line 326, in loads
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m    return _default_decoder.decode(s)
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m  File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00mTypeError: expected string or buffer
 [01;31m2013-10-03 16:49:25.908 TRACE nova.openstack.common.rpc.amqp  [01;35m [00m
2013-10-03 16:49:25.929  [01;31mERROR nova.openstack.common.rpc.common [ [01;36mreq-959589d1-c66d-41f8-bc0c-e874b7622a80  [00;36madmin admin [01;31m]  [01;35m [01;31mReturning exception expected string or buffer to caller [00m
2013-10-03 16:49:25.929  [01;31mERROR nova.openstack.common.rpc.common [ [01;36mreq-959589d1-c66d-41f8-bc0c-e874b7622a80  [00;36madmin

I dig into the code a bit and it seems to me that nova tries to ensure that the image is available on the destination host but it fails as there is no image associated to the instance due to the fact that it is booted from volume.

Should I file a bug report on this issue? 

Best regards,
Gibi