yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

** Also affects: nova/rocky
   Importance: Medium
     Assignee: Lee Yarwood (lyarwood)
       Status: 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/1786318

Title:
  Volume status remains "detaching" after a failure to detach a volume
  due to DeviceDetachFailed

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

Bug description:
  Description
  ===========
  Volume status remains "detaching" after a failure to detach a volume due to DeviceDetachFailed

  Steps to reproduce
  ==================
  Attempt to detach a volume while it is mounted and in-use within an instance.

  Expected result
  ===============
  Volume detach fails and the volume returns to in-use.

  Actual result
  =============
  Volume detach fails and the volume remains in a detaching state.

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

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

     Libirt + 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
  ==============

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