Ask Your Question

xroot's profile - activity

2019-02-11 10:28:05 -0500 received badge  Enthusiast
2017-09-11 08:40:07 -0500 received badge  Popular Question (source)
2017-09-08 14:33:09 -0500 commented question Boot from volume after the volume was migrated

No, the volume is not encrypted. Thanks.

2017-09-08 11:06:39 -0500 asked a question Boot from volume after the volume was migrated


Launch a new instance with the boot from volume option similar to this:

# nova boot --flavor 1 --block-device source=image,id=uuid,dest=volume,size=100,shutdown=preserve,bootindex=0 test-server-boot-volume0

Then stop the instance, detach the volume, and migrate the new volume to a different storage node. The volume retains the same volume UUID after migration.

After migration attaching the volume back to the same instance does not work. The error I get is this: ['HANDLE_INVALID', 'SR', 'OpaqueRef:67a0a74b-a461-9f08-8a4f-cfead65fcfd1']. The hypervisor is Xen.

Debugging this led me to this stacktrace:

File "/opt/mystack/nova/lib/python2.7/site-packages/nova/virt/", line 302, in attach device_type=self['device_type'], encryption=encryption)

File "/opt/mystack/nova/lib/python2.7/site-packages/nova/virt/xenapi/", line 429, in attach_volume mountpoint)

File "/opt/mystack/nova/lib/python2.7/site-packages/nova/virt/xenapi/", line 47, in attach_volume instance_name, dev_number, hotplug)

File "/opt/mystack/nova/lib/python2.7/site-packages/nova/virt/xenapi/", line 67, in _attach_volume connection_data)

File "/opt/mystack/nova/lib/python2.7/site-packages/nova/virt/xenapi/", line 272, in forget_sr session.call_xenapi("SR.forget", sr_ref)

File "/opt/mystack/nova/lib/python2.7/site-packages/nova/virt/xenapi/client/", line 210, in call_xenapi return session.xenapi_request(method, args)

File "/opt/mystack/nova/lib/python2.7/site-packages/", line 133, in xenapi_request result = _parse_result(getattr(self, methodname)(*full_params))

File "/opt/mystack/nova/lib/python2.7/site-packages/", line 203, in _parse_result raise Failure(result['ErrorDescription'])

The above code could be modified a little while I was debugging, but the call sequence is right.

Curiously, the same volume can be attached to a different VM and booted off of with no problems. It's only when I attach the volume to the original VM it belonged to before the volume migration.

Could you shed some light on this? Thank you!

2016-10-12 04:10:21 -0500 received badge  Nice Answer (source)
2016-05-14 21:19:35 -0500 received badge  Teacher (source)
2016-05-08 16:19:47 -0500 answered a question Instance will not launch. Neutron error on compute node.

A suggestion: please, check if the IPSet utility is installed. The compute node stack trace looks very similar to this: (



2016-03-07 20:27:18 -0500 received badge  Supporter (source)