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

Bug 1432876

Summary:	VM destroy call is not robust enough in cleanup flow
Product:	[oVirt] vdsm	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	Core	Assignee:	Milan Zamazal <mzamazal>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Israel Pinto <ipinto>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.19.11	CC:	bugs, lveyde
Target Milestone:	ovirt-4.1.2	Flags:	rule-engine: ovirt-4.1+
Target Release:	4.19.11
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-05-23 08:12:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michal Skrivanek 2017-03-16 09:59:33 UTC

When engine calls the VM destroy for a cleanup of a Down VM we assume and expect a clear "VM not found" return code from libvirt. It may happen that otther code is returned - unfortunately we do not really know the exact root cause, there were likely troubles with network connectivity. But the native libvirt tooling handles that gracefully, whereas oVirt assumes this is an error and triggers a chained reaction in engine.

Comment 1 Milan Zamazal 2017-03-16 10:06:56 UTC

The best way to handle that would be to perform cleanup of the VM in Vdsm. That should be enough in typical situations.

Comment 2 Israel Pinto 2017-05-04 08:35:10 UTC

Verify with:
VDSM: vdsm-4.19.11-1.el7ev.x86_64
RHEVM version: 4.1.2-0.1.el7

Steps:
In all cases check the logs(vdsm,engine) that the 'vm not found' not appear next to destry command.
Cases:
1. Create VM Run VM, Stop VM, Remove VM.
2. Create VM, Run VM, Migrate VM.

Results:
In all cases did not found the 'vm not found' next to destroy command.