yahoo-eng-team team mailing list archive

[OpenStack Infra <1727260@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/515008
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=ce531dd1b763704b9043ddde8e80ac99cd193660
Submitter: Zuul
Branch:    master

commit ce531dd1b763704b9043ddde8e80ac99cd193660
Author: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@xxxxxxxxxx>
Date:   Wed Oct 25 05:57:11 2017 -0400

    libvirt: disconnect volume from host during detach
    
    Under certain failure scenarios it may be that although the libvirt
    definition for the volume has been removed for the instance that the
    associated storage lun on the compute server may not have been fully
    cleaned up yet.
    
    In case users try an other attempt to detach volume we should not stop
    the process whether the device is not found in domain definition but
    try to disconnect the logical device from host.
    
    This commit makes the process to attempt a disconnect volume even if
    the device is not attached to the guest.
    
    Closes-Bug: #1727260
    Change-Id: I4182642aab3fd2ffb1c97d2de9bdca58982289d8
    Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@xxxxxxxxxx>


** Changed in: nova
       Status: In Progress => Fix Released

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

Title:
   Nova assumes that a volume is fully detached from the compute if the
  volume is not defined in the instance's libvirt definition

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) pike series:
  Confirmed
Status in OpenStack Compute (nova) queens series:
  In Progress

Bug description:
  During a volume detach operation, Nova compute attempts to remove the
  volume from libvirt for the instance before proceeding to remove the
  storage lun from the underlying compute host. If Nova discovers that
  the volume was not found in the instance's libvirt definition then it
  ignores that error condition and returns (after issuing a warning
  message "Ignoring DiskNotFound exception while detaching").

  However, under certain failure scenarios it may be that although the
  libvirt definition for the volume has been removed for the instance
  that the associated storage lun on the compute server may not have
  been fully cleaned up yet.

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