yahoo-eng-team team mailing list archive

[melanie witt <1633033@xxxxxxxxxxxxxxxxxx>]

lyarwood confirmed on IRC in the #openstack-nova channel today that this
bug has been fixed by:

https://review.openstack.org/460243

which landed in queens. So the fix is available in as of version
17.0.0.0b3.

** Changed in: nova
   Importance: Undecided => Medium

** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1633033

Title:
  live migration with encrypted volume fails

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  When live migrating an instance with an encrypted volume it fails to
  detach the encrypted volume from the source and attaches at the target
  as an unencrypted volume.

  I do see the encrypted volume connector on the source but not on the
  target

  ls -l /dev/disk/by-path
  total 0
  lrwxrwxrwx 1 root root 121 Oct 13 10:26 ip-192.168.16.20:3260-iscsi-iqn.2010-10.org.openstack:volume-1a17d61f-7f44-450e-b040-a0baebdb0466-lun-1 -> /dev/mapper/crypt-ip-192.168.16.20:3260-iscsi-iqn.2010-10.org.openstack:volume-1a17d61f-7f44-450e-b040-a0baebdb0466-lun-1
  lrwxrwxrwx 1 root root   9 Oct 13 10:36 ip-192.168.16.20:3260-iscsi-iqn.2010-10.org.openstack:volume-76909639-61bc-4abd-9a1e-fd5624bb8fc1-lun-1 -> ../../sdd

  Target

  ls -l /dev/disk/by-path
  total 0
  lrwxrwxrwx 1 root root  9 Oct 13 10:48 ip-192.168.16.20:3260-iscsi-iqn.2010-10.org.openstack:volume-1a17d61f-7f44-450e-b040-a0baebdb0466-lun-1 -> ../../sdb
  lrwxrwxrwx 1 root root  9 Oct 13 10:48 ip-192.168.16.20:3260-iscsi-iqn.2010-10.org.openstack:volume-76909639-61bc-4abd-9a1e-fd5624bb8fc1-lun-1 -> ../../sdc

  The instance can still access encrypted volume, but the data
  disappears when you umount/mount the device so I guess it looked ok at
  first due to filesystem caching

  The live migration fails in post migrate on the source due to an error
  trying to detach the encrypted volume (see bug
  https://bugs.launchpad.net/os-brick/+bug/1631318, which I'll close
  now)

  Subsequent attempts to detach the volume from the instance (after
  manually updating it to say it is on the target and active, see
  https://bugs.launchpad.net/nova/+bug/1628606.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1633033/+subscriptions