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

Bug 1881471

Summary:	Hosted Engine VM gets devices unplugged
Product:	[oVirt] ovirt-engine	Reporter:	Liran Rotenberg <lrotenbe>
Component:	BLL.Virt	Assignee:	Liran Rotenberg <lrotenbe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.1.4	CC:	ahadas, bugs, dfodor, pagranat
Target Milestone:	ovirt-4.4.3	Keywords:	Triaged
Target Release:	---	Flags:	pm-rhel: ovirt-4.4+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.3-6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-11 06:41:34 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 Liran Rotenberg 2020-09-22 13:28:41 UTC

Since the first boot of the HE VM is not correlate with the engine DB, this might result a bad correlation of devices each time the HE VM boots.

It may result in having only warnings in the engine log and libvirt will re-add devices. Or, in the worse case unusable functionality to the HE VM due to unplugged VM devices.

We added support for old VMs correlation in BZ 1850220. But the problematic correlation seems to appear on HE VM nonetheless.

Comment 1 Polina 2020-09-29 07:06:57 UTC

related https://bugzilla.redhat.com/show_bug.cgi?id=1861753#c5

Comment 2 Liran Rotenberg 2020-09-29 13:07:07 UTC

This is seem to be relevant only to virtio-scsi controller. The result is having 2 virtio-scsi devices in the DB. One is managed and unplugged the other is unmanaged and plugged.
On HE VM creation the disk interface is virtio and generally the controller does exist and functional. Therefore there is no real harm to functionality.

The reason for this seems to be the HE VM deployment and non-existing alias on the first boot(using virt-installer).

Comment 5 Nikolai Sednev 2020-10-11 10:14:48 UTC

Works as expected from Comment#4, no original error detected.
Tested on:
ovirt-engine-setup-4.4.2.6-0.2.el8ev.noarch
rhvm-appliance-4.4-20200915.0.el8ev.x86_64
ovirt-hosted-engine-ha-2.4.4-1.el8ev.noarch
ovirt-hosted-engine-setup-2.4.6-2.el8ev.noarch
Linux 4.18.0-240.el8.x86_64 #1 SMP Wed Sep 23 05:13:10 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux release 8.3 (Ootpa)

Comment 6 Sandro Bonazzola 2020-11-11 06:41:34 UTC

This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.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.