[Yahoo-eng-team] [Bug 1786318] Re: Volume status remains "detaching" after a failure to detach a volume due to DeviceDetachFailed
** Changed in: nova/rocky Status: Fix Released => In Progress ** Tags added: rocky-rc-potential -- 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: In Progress 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1786318] Re: Volume status remains "detaching" after a failure to detach a volume due to DeviceDetachFailed
** 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1786318] Re: Volume status remains "detaching" after a failure to detach a volume due to DeviceDetachFailed
Reviewed: https://review.openstack.org/590439 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3a4b4b91b0bee514d47a67f6a5f9c4ab9ae7f7d8 Submitter: Zuul Branch:master commit 3a4b4b91b0bee514d47a67f6a5f9c4ab9ae7f7d8 Author: Lee Yarwood Date: Thu Aug 9 17:43:50 2018 +0100 block_device: Rollback volumes to in-use on DeviceDetachFailed The call to os-roll_detaching was dropped when I3800b466a50b1e5f5d1e8c8a963d9a6258af67ee started to catch and reraise DeviceDetachFailed. This call is required to ensure a volume returns to an in-use state when the instance is unable to detach. Closes-Bug: #1786318 Change-Id: I6b3dc09acc6f360806ce0ef8c8a65addbf4a8c51 ** 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/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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
[Yahoo-eng-team] [Bug 1786318] Re: Volume status remains "detaching" after a failure to detach a volume due to DeviceDetachFailed
** Changed in: nova Importance: Undecided => Medium ** Also affects: nova/queens Importance: Undecided Status: New ** Also affects: nova/pike Importance: Undecided Status: New ** Changed in: nova/pike Status: New => Confirmed ** Changed in: nova/queens Status: New => Confirmed ** Changed in: nova/pike Importance: Undecided => Medium ** Changed in: nova/queens Importance: Undecided => Medium -- 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): In Progress Status in OpenStack Compute (nova) pike series: Confirmed Status in OpenStack Compute (nova) queens series: Confirmed 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
