Bug 1424481 - Rollback of failed live migration with attached volume fails on destination
Summary: Rollback of failed live migration with attached volume fails on destination
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 8.0 (Liberty)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Upstream M2
: 14.0 (Rocky)
Assignee: Lee Yarwood
QA Contact: Prasanth Anbalagan
URL:
Whiteboard:
: 1353147 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-17 17:17 UTC by Matthew Booth
Modified: 2021-12-10 14:58 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-06 08:57:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 579125 0 None None None 2018-06-29 11:21:54 UTC
Red Hat Issue Tracker OSP-11276 0 None None None 2021-12-10 14:58:58 UTC

Description Matthew Booth 2017-02-17 17:17:18 UTC
Description of problem:
This bug comes out of bug 1421946. In that bug we're doing a live migration of an instance with an attached volume, which fails. The live migration failure itself is not the subject of this bug.

During the rollback we somehow end up calling ComputeManager._driver_detach_volume on the *destination*, which attempts to detach the volume from the ephemeral destination domain. This fails with:

libvirtError: Requested operation is not valid: cannot modify device on transient domain

The logs aren't 100% clear, but I am guessing this is called from _rollback_live_migration() when it calls self.compute_rpcapi.remove_volume_connection(context, instance, bdm.volume_id, dest). Note that the dest target is explicit.

Failure during rollback means that the rollback is incomplete, which is likely wasting resources.

Comment 5 Lee Yarwood 2018-03-15 14:47:22 UTC
*** Bug 1353147 has been marked as a duplicate of this bug. ***

Comment 12 Lee Yarwood 2018-07-06 08:57:34 UTC
This was resolved during Pike and backedport to stable/ocata and stable/newton:

https://review.openstack.org/#/q/I95948721a0119f5f54dbe50d4455fd47d422164b

Closing as CURRENTRELEASE.

Comment 13 Lee Yarwood 2018-07-17 13:23:23 UTC
To be clear this fix landed in openstack-nova in the following releases, OSP 10  >=14.0.8 and OSP 11 >=15.0.7. All versions of openstack-nova shipped with OSP 12 and 13 have this fix at release.


Note You need to log in before you can comment on or make changes to this bug.