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

Bug 1795246

Summary:	WGT ISO on data domain is always attached to Win VMs
Product:	[oVirt] ovirt-engine	Reporter:	Petr Matyáš <pmatyas>
Component:	Backend.Core	Assignee:	Liran Rotenberg <lrotenbe>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Beni Pelled <bpelled>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.0	CC:	bugs, lrotenbe, rbarry
Target Milestone:	ovirt-4.4.0	Flags:	pm-rhel: ovirt-4.4+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.0 gitb5b5c99ca2f	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-20 20:02:39 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:
Bug Depends On:	1722519
Bug Blocks:

Description Petr Matyáš 2020-01-27 14:26:22 UTC

Description of problem:
ISO with latest WGT is always attached to Win VMs even though I just finished installing it and there is no notification that I have old GT.

Version-Release number of selected component (if applicable):
ovirt-engine-4.4.0-0.17.master.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. install latest WGT on Win VM
2. shutdown and start the VM (you can do this multiple times so it's not reporting new version is available on shutdown)

Actual results:
VM will have latest WGT ISO attached

Expected results:
there is no ISO attached when it is not necessary (latest WGT is installed)

Additional info:

Comment 1 Liran Rotenberg 2020-01-27 14:32:02 UTC

Can you please check if the WGT are reported to the engine?
Under the VM -> Applications or in the engine DB (vm_dynamic table - app_list)
If it's not updated, please let the VM run for a while to get it updated.

Comment 2 Petr Matyáš 2020-01-27 14:34:37 UTC

It is reported.

It's showing 'RHEV-Tools 4.3.10' as it's actually not showing any warning.

Comment 3 Liran Rotenberg 2020-01-27 14:42:28 UTC

OK, can you check the engine-config value for WGT?
# engine-config -g GuestToolsSetupIsoPrefix

Comment 4 Petr Matyáš 2020-01-27 15:14:03 UTC

[root@engine ~]# engine-config -g GuestToolsSetupIsoPrefix
Error fetching GuestToolsSetupIsoPrefix value: no such entry. Please verify key name and property file support.

This is an updated setup from 4.2 (through 4.3) so probably there is a bug hiding in there.

Comment 5 Liran Rotenberg 2020-01-28 12:49:38 UTC

There is a difference in 'AgentAppName' from the upgraded environment.
Therefore, when seeing RHEV-AGENT64 or RHEV-AGENT 4.3.3 it will be considered.
When considered, 4.3.3 will always be < 4.3.10 and the CD will be attached.

Comment 6 Sandro Bonazzola 2020-03-13 09:31:12 UTC

This bug is in modified and targeting 4.4.1. Can we re-target to 4.4.0 and move to QE?

Comment 7 Beni Pelled 2020-04-23 12:35:47 UTC

Verified with:
- RHV 4.4.0-0.32.master.el8ev
- libvirt-6.0.0-17.module+el8.2.0+6257+0d066c28.x86_64
- vdsm-4.40.13-1.el8ev.x86_64

Verification steps:
1. Create a Windows VM > start is > make sure guest-agent is installed and running.
2. Shutdown and re-start the VM > make sure WGT isn't attached as a CD-ROM.

Result:
- The WGT was attached on stage 1 and removed after shutdown and restart the server, RHEV-AGENT64 is listed under VM > Applications.

Comment 8 Sandro Bonazzola 2020-05-20 20:02:39 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

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