yahoo-eng-team team mailing list archive

[Lee Yarwood <lyarwood@xxxxxxxxxx>]

*** This bug is a duplicate of bug 1669857 ***
    https://bugs.launchpad.net/bugs/1669857

** This bug has been marked a duplicate of bug 1669857
   libvirt.VIR_DOMAIN_AFFECT_CONFIG provided when detaching volumes during LM rollback

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

Title:
  Libvirt LM rollback fails due to the destination domain being
  transient and unable to detach devices.

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  Description
  ===========
  Libvirt LM rollback fails due to the destination domain being transient and unable to detach devices.

  Steps to reproduce
  ==================
  - Attempt to LM an instance with volumes attached
  - Cause the LM to fail

  Expected result
  ===============
  Volumes disconnected from the destination host.

  Actual result
  =============
  Volumes still connected to the destination host.

  Environment
  ===========
  1. Exact version of OpenStack you are running. See the following
    list for all releases: http://docs.openstack.org/releases/

     origin/master

  2. Which hypervisor did you use?
     (For example: Libvirt + KVM, Libvirt + XEN, Hyper-V, PowerKVM, ...)
     What's the version of that?

     Libvirt + kvm

  2. Which storage type did you use?
     (For example: Ceph, LVM, GPFS, ...)
     What's the version of that?

     N/A

  3. Which networking type did you use?
     (For example: nova-network, Neutron with OpenVSwitch, ...)

     N/A

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