Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1703441

Summary:	[OSP10] Add missing libvirt exception during device detach
Product:	Red Hat OpenStack	Reporter:	Lee Yarwood <lyarwood>
Component:	openstack-nova	Assignee:	Lee Yarwood <lyarwood>
Status:	CLOSED ERRATA	QA Contact:	OSP DFG:Compute <osp-dfg-compute>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	10.0 (Newton)	CC:	dasmith, dhill, eglynn, jhakimra, kchamart, sbauza, sgordon, vromanso
Target Milestone:	async	Keywords:	Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-nova-14.1.0-49.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-07-10 09:19:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lee Yarwood 2019-04-26 12:30:35 UTC

Description of problem:

Add missing libvirt exception during device detach
https://review.opendev.org/#/c/651642/

It turns out that when detaching a device libvirt can raise a
libvirt.VIR_ERR_INTERNAL_ERROR exception with an error log of
"unable to execute QEMU command 'device_del': Device <foo> not found".

Add this exception to the existing "not found" case which currently
handles only libvirt.VIR_ERR_OPERATION_FAILED.

Version-Release number of selected component (if applicable):
OSP 10

How reproducible:
Always

Steps to Reproduce:
1. Cause a libvirtError of type VIR_ERR_INTERNAL_ERROR during volume detach.

Actual results:
Underlying volume is not disconnected.

Expected results:
Volume disconnected.

Additional info:

Comment 9 errata-xmlrpc 2019-07-10 09:19:01 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:1715