Bug 1718852

Summary:	Track devices with user aliases instead of properties
Product:	[oVirt] ovirt-engine	Reporter:	Ryan Barry <rbarry>
Component:	BLL.Virt	Assignee:	Tomasz Barański <tbaransk>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	future	CC:	ahadas, bugs, michal.skrivanek, nsimsolo
Target Milestone:	ovirt-4.4.1	Keywords:	FutureFeature
Target Release:	---	Flags:	rbarry: ovirt-4.4? pm-rhel: planning_ack? pm-rhel: devel_ack+ pm-rhel: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhv-4.4.0-29	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-08-05 06:24:37 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 Ryan Barry 2019-06-10 12:13:29 UTC

Description of problem:
Since the introduction of domain XML, device tracking for VMs does not follow user aliases, since they were not supported everywhere. This leads to inconsistent/messy tracking of devices, especially disks, and can be cleaned up with CL 4.4

We should use aliases in order to associate Devices:VMs

Comment 1 Michal Skrivanek 2019-06-11 10:01:39 UTC

also NICs. In general all devices since 4.2 get a unique alias(VmDevice UUID)

Comment 3 Nisim Simsolo 2020-07-09 07:30:52 UTC

Verified:
ovirt-engine-4.4.1.7-0.3.el8ev
vdsm-4.40.22-1.el8ev.x86_64
qemu-kvm-4.2.0-28.module+el8.2.1+7211+16dfe810.x86_64
libvirt-daemon-6.0.0-25.module+el8.2.1+7154+47ffd890.x86_64

Verification scenario:
QE manual and automated testing did not encounter issues related to this bug.

Comment 4 Sandro Bonazzola 2020-08-05 06:24:37 UTC

This bugzilla is included in oVirt 4.4.1 release, published on July 8th 2020.

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