← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1889108] [NEW] failures during driver.pre_live_migration remove source attachments during rollback

 

Public bug reported:

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

$subject, the initial rollback and removal of any destination volume
attachments is then repeated for the source volume attachments, leaving
the volumes connected on the host but listed as `available` in cinder.

Steps to reproduce
==================
Cause a failure during the call to driver.pre_live_migration with volumes attached.

Expected result
===============
Any volume attachments for the destination host are deleted during the rollback.

Actual result
=============
Both sets of volumes attachments for the destination *and* the source are removed.

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

   eeeb964a5f65e6ac31dfb34b1256aaf95db5ba3a

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

Logs & Configs
==============

When live-migration fails with attached volume changed to active and still in nova
https://bugzilla.redhat.com/show_bug.cgi?id=1860914

** Affects: nova
     Importance: High
     Assignee: Lee Yarwood (lyarwood)
         Status: Confirmed


** Tags: cinder live-migration volumes

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

Title:
  failures during driver.pre_live_migration remove source attachments
  during rollback

Status in OpenStack Compute (nova):
  Confirmed

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

  $subject, the initial rollback and removal of any destination volume
  attachments is then repeated for the source volume attachments,
  leaving the volumes connected on the host but listed as `available` in
  cinder.

  Steps to reproduce
  ==================
  Cause a failure during the call to driver.pre_live_migration with volumes attached.

  Expected result
  ===============
  Any volume attachments for the destination host are deleted during the rollback.

  Actual result
  =============
  Both sets of volumes attachments for the destination *and* the source are removed.

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

     eeeb964a5f65e6ac31dfb34b1256aaf95db5ba3a

  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

  Logs & Configs
  ==============

  When live-migration fails with attached volume changed to active and still in nova
  https://bugzilla.redhat.com/show_bug.cgi?id=1860914

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


Follow ups