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

Bug 1552713

Summary:	Unknown VMs are added on libvirt Undefined event
Product:	[oVirt] vdsm	Reporter:	Petr Kotas <pkotas>
Component:	General	Assignee:	Milan Zamazal <mzamazal>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Vitalii Yerys <vyerys>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.20.19	CC:	bugs, mzamazal
Target Milestone:	ovirt-4.2.3	Flags:	rule-engine: ovirt-4.2+
Target Release:	---
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:	2018-05-10 06:32:50 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 Petr Kotas 2018-03-07 15:28:21 UTC

The VSDM keeps adding the VM once it has been deleted. The code doing this is in 
clientIF.py:608.

The culprit is the libvirt, which fires the undefined event https://libvirt.org/html/libvirt-libvirt-domain.html#virDomainEventType

The VDSM should not add unknown wm for the "undefined event"

Comment 1 Milan Zamazal 2018-03-08 10:58:52 UTC

Actually Vdsm doesn't add a VM in that case, it just tracks the VM id as unknown. It keeps asking libvirt about it and pollutes the log with related debug messages.

If libvirt doesn't know a VM with the given id, Vdsm should forget it and not ask about it forever. I'll fix that.

Comment 2 Yaniv Kaul 2018-03-15 13:59:38 UTC

Is this on track to 4.2.2? If not, please defer to 4.2.3.

Comment 3 Milan Zamazal 2018-03-15 14:04:01 UTC

Deferred.

Comment 4 Vitalii Yerys 2018-04-26 17:29:45 UTC

Verified on
rhv-release-4.2.3-2-001.noarch
vdsm-4.20.26-1.el7ev.x86_64

Comment 5 Sandro Bonazzola 2018-05-10 06:32:50 UTC

This bugzilla is included in oVirt 4.2.3 release, published on May 4th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.3 release, it has been closed with a resolution of CURRENT RELEASE.

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