[openstack-dev] [nova] [cinder] Issue with live migration of instances with encrypted volumes
Carlton, Paul (Cloud Services)
paul.carlton2 at hpe.com
Tue Nov 1 12:02:55 UTC 2016
Yes, thanks, but the thing is this does not occur with regular volumes!
The process seems to be you need to connect the volume then the encryptor.
In pre migration at the destination I connect the volume and then setup the encryptor and that works fine, but in post migration
at destination it rebuilds the instance xml and defines the vm which calls _get_guest_storage_config which does another call to
connect_volume. This seems redundant to me, because it is already connected,
but it works for normal volumes and if I bypass it for encrypted volumes
it just fails with the same error when the same function is
called as part of
a subsequent hard
Hewlett Packard Enterprise
Bristol BS34 8QZ
Office: +44 (0) 1173 162189
Mobile: +44 (0)7768 994283
Email: paul.carlton at hpe.com
Hewlett-Packard Enterprise Limited registered Office: Cain Road, Bracknell, Berks RG12 1HN Registered No: 690597 England.
The contents of this message and any attachments to it are confidential and may be legally privileged. If you have received this message in error, you should delete it from your system immediately and advise the sender. To any recipient of this message within HP, unless otherwise stated you should consider this message and attachments as "HP CONFIDENTIAL".
From: Daniel P. Berrange <berrange at redhat.com>
Sent: 01 November 2016 11:29:51
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] [cinder] Issue with live migration of instances with encrypted volumes
On Tue, Nov 01, 2016 at 11:22:25AM +0000, Carlton, Paul (Cloud Services) wrote:
> I'm working on a bug https://bugs.launchpad.net/nova/+bug/1633033 with the live migration of
> instances with encrypted volumes. I've submitted a work in progress version of a patch
> https://review.openstack.org/#/c/389608 but I can't overcome an issue with an iscsi command
> failure that only occurs for encrypted volumes during the post migration processing, see
> Does anyone have any thoughts on how to proceed with this issue?
No particular ideas, but I wanted to point out that the scsi_id command
shown in that stack trace has a device path that points to the raw
iSCSI LUN, not to the dm-crypt overlay. So it looks like you're hitting
a failure before you get the encryption part, so encryption might be
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
Until today, libvirt has used a 3 digit version number for monthly releases off the git master branch, and a 4 digit version number for maintenance releases off ...
|: http://libvirt.org -o- http://virt-manager.org :|
libvirt: The virtualization API<http://libvirt.org/>
The virtualization API libvirt is: A toolkit to interact with the virtualization capabilities of recent versions of Linux (and other OSes), see our project ...
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev