[Bug 1398999] Related fix merged to nova (master)

[OpenStack Infra]

Reviewed:  https://review.openstack.org/252506
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f0d5fc61916f41214da580097a09136e4ed2c99a
Submitter: Jenkins
Branch:    master

commit f0d5fc61916f41214da580097a09136e4ed2c99a
Author: Pawel Koniszewski <pawel.koniszewski at intel.com>
Date:   Fri Dec 11 03:28:50 2015 +0100

    Get list of disks to copy early to avoid multiple DB hits
    
    To support selective block migration we need to read block devices
    from nova block device mappings instead of libvirt block info.
    It means that in current implementation we would call
    _live_migration_copy_disk_paths two times - from
    live_migration_operations and from live_migration_monitor.
    To avoid that this change gets disk paths early and pass them as
    and additional paremeter to live migration monitor.
    
    Change-Id: Ic894cfc7374ba06b436b2a76a5984012d1dba3a5
    Related-bug: #1398999

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1398999

Title:
  Block migrate with attached volumes copies volumes to themselves

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) juno series:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in nova package in Ubuntu:
  Triaged
Status in libvirt source package in Trusty:
  Confirmed
Status in nova source package in Trusty:
  Triaged
Status in libvirt source package in Utopic:
  Won't Fix
Status in nova source package in Utopic:
  Won't Fix
Status in libvirt source package in Vivid:
  Confirmed
Status in nova source package in Vivid:
  Triaged
Status in libvirt source package in Wily:
  Fix Released
Status in nova source package in Wily:
  Triaged

Bug description:
  When an instance with attached Cinder volumes is block migrated, the
  Cinder volumes are block migrated along with it. If they exist on
  shared storage, then they end up being copied, over the network, from
  themselves to themselves. At a minimum, this is horribly slow and de-
  sparses a sparse volume; at worst, this could cause massive data
  corruption.

  More details at http://lists.openstack.org/pipermail/openstack-
  dev/2014-June/038152.html

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