Public bug reported:

Description
===========

Volume-backed instances fails to migrate when config-drive is enabled(even with 
vfat). 
Migration fails with exception.InvalidSharedStorage during 
check_can_live_migrate_source method execution 
https://github.com/openstack/nova/blob/545d8d8666389f33601b0b003dec844004694919/nova/virt/libvirt/driver.py#L5388

The root cause:
https://github.com/openstack/nova/blob/545d8d8666389f33601b0b003dec844004694919/nova/virt/libvirt/driver.py#L5344
 - flags is calculated incorrectly.


Steps to reproduce
==================
1. use vfat as config drive format, no shared storage like nfs;
2. boot instance from volume;
3. try to live-migrate instance;

Expected result
===============
instance migrated successfully

Actual result
=============
live-migration is not even started:
root@node-1:~# nova live-migration server00 node-4.test.domain.local
ERROR (BadRequest): Migration pre-check error: Cannot block migrate instance 
f477e6da-4a04-492b-b7a6-e57b7823d301 with mapped volumes. Selective block 
device migration feature requires libvirt version 1.2.17 (HTTP 400) 
(Request-ID: req-4e0fce45-8b7c-43c0-90e7-cc929d2d60a1)

Environment
===========

multinode env, without file based shared storages like NFS.
driver libvirt/kvm
openstack branch stable/mitaka,
should also be valid for master.

** Affects: nova
     Importance: Medium
         Status: Confirmed


** Tags: live-migration

** Summary changed:

- volume-backed  instances with config-drive type vfat  live-migration fails 
+ live-migration fails for volume-backed  instances with config-drive type vfat

-- 
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/1589457

Title:
  live-migration fails for volume-backed  instances with config-drive
  type vfat

Status in OpenStack Compute (nova):
  Confirmed

Bug description:
  Description
  ===========

  Volume-backed instances fails to migrate when config-drive is enabled(even 
with vfat). 
  Migration fails with exception.InvalidSharedStorage during 
check_can_live_migrate_source method execution 
https://github.com/openstack/nova/blob/545d8d8666389f33601b0b003dec844004694919/nova/virt/libvirt/driver.py#L5388

  The root cause:
  
https://github.com/openstack/nova/blob/545d8d8666389f33601b0b003dec844004694919/nova/virt/libvirt/driver.py#L5344
 - flags is calculated incorrectly.

  
  Steps to reproduce
  ==================
  1. use vfat as config drive format, no shared storage like nfs;
  2. boot instance from volume;
  3. try to live-migrate instance;

  Expected result
  ===============
  instance migrated successfully

  Actual result
  =============
  live-migration is not even started:
  root@node-1:~# nova live-migration server00 node-4.test.domain.local
  ERROR (BadRequest): Migration pre-check error: Cannot block migrate instance 
f477e6da-4a04-492b-b7a6-e57b7823d301 with mapped volumes. Selective block 
device migration feature requires libvirt version 1.2.17 (HTTP 400) 
(Request-ID: req-4e0fce45-8b7c-43c0-90e7-cc929d2d60a1)

  Environment
  ===========

  multinode env, without file based shared storages like NFS.
  driver libvirt/kvm
  openstack branch stable/mitaka,
  should also be valid for master.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to