yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #73026
[Bug 1773318] [NEW] live migration failed when target host have different image_type than instance disk
Public bug reported:
Description
===========
When a target host is preparing live-migration, it creates disk
according nova.conf setting CONF.libvirt.images_type
and do not preserve image type disk of instance, making fail live-migration
Use case:
===========
We have to convert a set of existing instance from qcow2 to raw.
In order to proceed we changed images_type of compute hosts to raw,
So that newly spawn instances are in raw.
It mean that during some time(until migration is done)
we may have both qcow2 and raw instances sharing same host(now configured as raw).
We still need to have live-migration working on our legacy instance in qcow2 to other
host now configured as raw (we want to keep qcow2 format on destination)
Steps to reproduce
==================
1) spawn one qcow2 instance on hostA
2) change settings images_type to raw on hostA and hostB
2) try to live migrate instance qcow2 from hostA to hostB
4) the issue occur:
hostb prepare target disk in raw and qemu on hostb start with original xml settings expecting a qcow2 disk
/var/log/libvirt/qemu/instance-000170c9.log:2018-05-23T07:23:49.936829Z qemu-system-x86_64: -drive file=/home/instances/bdf1cea0-4d90-4061-bd1e-e20296a97f0e/disk,format=qcow2,...: Image is not in qcow2 format
Expected result
===============
instance keep its original format on target host even if target host have different image type.
Proposed solution:
keep original disk type of instance (patch to follow)
** Affects: nova
Importance: Undecided
Status: New
--
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/1773318
Title:
live migration failed when target host have different image_type than
instance disk
Status in OpenStack Compute (nova):
New
Bug description:
Description
===========
When a target host is preparing live-migration, it creates disk
according nova.conf setting CONF.libvirt.images_type
and do not preserve image type disk of instance, making fail live-migration
Use case:
===========
We have to convert a set of existing instance from qcow2 to raw.
In order to proceed we changed images_type of compute hosts to raw,
So that newly spawn instances are in raw.
It mean that during some time(until migration is done)
we may have both qcow2 and raw instances sharing same host(now configured as raw).
We still need to have live-migration working on our legacy instance in qcow2 to other
host now configured as raw (we want to keep qcow2 format on destination)
Steps to reproduce
==================
1) spawn one qcow2 instance on hostA
2) change settings images_type to raw on hostA and hostB
2) try to live migrate instance qcow2 from hostA to hostB
4) the issue occur:
hostb prepare target disk in raw and qemu on hostb start with original xml settings expecting a qcow2 disk
/var/log/libvirt/qemu/instance-000170c9.log:2018-05-23T07:23:49.936829Z qemu-system-x86_64: -drive file=/home/instances/bdf1cea0-4d90-4061-bd1e-e20296a97f0e/disk,format=qcow2,...: Image is not in qcow2 format
Expected result
===============
instance keep its original format on target host even if target host have different image type.
Proposed solution:
keep original disk type of instance (patch to follow)
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1773318/+subscriptions