Bug 1273226 - Live migration fails when the instance has a config_drive_format=iso9660
Summary: Live migration fails when the instance has a config_drive_format=iso9660
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 8.0 (Liberty)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: async
: 9.0 (Mitaka)
Assignee: Michal Pryc
QA Contact: Mike Abrams
URL:
Whiteboard:
Depends On:
Blocks: 1281573
TreeView+ depends on / blocked
 
Reported: 2015-10-20 01:20 UTC by Stephen Gordon
Modified: 2020-06-11 12:44 UTC (History)
19 users (show)

Fixed In Version: openstack-nova-13.1.2-1.el7ost.src.rpm
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-08 17:45:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1246201 0 None None None Never
OpenStack gerrit 227278 0 None MERGED Allow block live migration of an instance with attached volumes 2020-04-08 22:30:22 UTC
OpenStack gerrit 234659 0 None MERGED [libvirt] Live migration fails when config_drive_format=iso9660 2020-04-08 22:30:22 UTC
OpenStack gerrit 252506 0 None MERGED Get list of disks to copy early to avoid multiple DB hits 2020-04-08 22:30:22 UTC
OpenStack gerrit 365420 0 None MERGED [libvirt] Live migration fails when config_drive_format=iso9660 2020-04-08 22:30:22 UTC
Red Hat Product Errata RHBA-2017:0467 0 normal SHIPPED_LIVE openstack-nova bug fix advisory 2017-03-08 22:44:46 UTC

Description Stephen Gordon 2015-10-20 01:20:15 UTC 
Description of problem:

This error has occurred under the following situations.

・ Live migration of volume backed instance which has a config-drive
・ Block migration of instance which has a config-drive

we have to create a config-drive on destination host in pre-live-migration.
Comment 2 Stephen Gordon 2015-11-06 15:17:54 UTC 
NB: When using VFAT for the configuration drive this issue should not exist.
Comment 3 Eoghan Glynn 2015-12-11 11:18:45 UTC 
@steveg: would simply using VFAT instead be a sufficient workaround in this case?
Comment 4 Stephen Gordon 2016-01-12 22:26:55 UTC 
(In reply to Eoghan Glynn from comment #3)
> @steveg: would simply using VFAT instead be a sufficient workaround in this
> case?

When I queried the relevant partner on this the answer was no. They had a specific reason they needed to use iso9660.
Comment 18 Tzach Shefi 2017-01-22 10:28:35 UTC 
Removed Depends on flag on 1412661,  
was marked by mistake.
Comment 22 errata-xmlrpc 2017-03-08 17:45:06 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0467.html
Note You need to log in before you can comment on or make changes to this bug.