yahoo-eng-team team mailing list archive

[Tao Li <litao7050@xxxxxxxxxxxxx>]

Public bug reported:

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


Volume-backed instances fails to live-migrate when config-drive is enabled, the config drive uses iso9660 format. When the instance booted from volume, the libvirt raised an exception: pre-creation of storage targets for incremental storage migration is not supported. In live-migration process, nova considers this instance to live-migrate with block-migrate, but the config drive is copied from source host to dest host in live-migration, and no local disk to migrated by libvirt, so libvirt raised this exception. I think this is a bug. If there is no local disk to migrate by libvirt, we shouldn't use block-migrate.

Steps to reproduce
==================
1. Boot a instance with volume and configdrive.
2. Live-migrate the instance with block-migrate=auto

Expected result
===============
The instance live-migrate successfully.

Actual result
=============
The instance failed to live-migrate, and livrit raised an exception. The message is pre-creation of storage targets for incremental storage migration is not supported.

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

Openstack verison: Pike
Livirt version: 3.2.0
Qemu version: 2.9.0

In nova.conf
[libvirt]
images_type = raw

** Affects: nova
     Importance: Undecided
     Assignee: Tao Li (eric-litao)
         Status: New

** Description changed:

  Description
  ===========
- Openstack verison: Pike
- Livirt version: 3.2.0
- Qemu version: 2.9.0
  
- In nova.conf 
- [libvirt]
- images_type = raw
  
- Volume-backed instances fails to live-migrate when config-drive is
- enabled, the config drive uses iso9660 format. When the instance booted
- from volume, the libvirt raised an exception: pre-creation of storage
- targets for incremental storage migration is not supported. In live-
- migration process, nova considers this instance to live-migrate with
- block-migrate, but the config drive is copied from source host to dest
- host in live-migration, and no local disk to migrated by libvirt, so
- libvirt raised this exception. I think this is a bug. If there is no
- local disk to migrate by libvirt, we shouldn't use block-migrate.
+ Volume-backed instances fails to live-migrate when config-drive is enabled, the config drive uses iso9660 format. When the instance booted from volume, the libvirt raised an exception: pre-creation of storage targets for incremental storage migration is not supported. In live-migration process, nova considers this instance to live-migrate with block-migrate, but the config drive is copied from source host to dest host in live-migration, and no local disk to migrated by libvirt, so libvirt raised this exception. I think this is a bug. If there is no local disk to migrate by libvirt, we shouldn't use block-migrate.
  
  Steps to reproduce
  ==================
  1. Boot a instance with volume and configdrive.
  2. Live-migrate the instance with block-migrate=auto
  
  Expected result
  ===============
  The instance live-migrate successfully.
  
  Actual result
  =============
  The instance failed to live-migrate, and livrit raised an exception. The message is pre-creation of storage targets for incremental storage migration is not supported.
  
  Environment
  ===========
+ 
+ Openstack verison: Pike
+ Livirt version: 3.2.0
+ Qemu version: 2.9.0
+ 
+ In nova.conf
+ [libvirt]
+ images_type = raw

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

Title:
  Live migration failed when the instance is booted with volume and
  config drive

Status in OpenStack Compute (nova):
  New

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

  
  Volume-backed instances fails to live-migrate when config-drive is enabled, the config drive uses iso9660 format. When the instance booted from volume, the libvirt raised an exception: pre-creation of storage targets for incremental storage migration is not supported. In live-migration process, nova considers this instance to live-migrate with block-migrate, but the config drive is copied from source host to dest host in live-migration, and no local disk to migrated by libvirt, so libvirt raised this exception. I think this is a bug. If there is no local disk to migrate by libvirt, we shouldn't use block-migrate.

  Steps to reproduce
  ==================
  1. Boot a instance with volume and configdrive.
  2. Live-migrate the instance with block-migrate=auto

  Expected result
  ===============
  The instance live-migrate successfully.

  Actual result
  =============
  The instance failed to live-migrate, and livrit raised an exception. The message is pre-creation of storage targets for incremental storage migration is not supported.

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

  Openstack verison: Pike
  Livirt version: 3.2.0
  Qemu version: 2.9.0

  In nova.conf
  [libvirt]
  images_type = raw

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