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:
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.
It is reported. It's showing 'RHEV-Tools 4.3.10' as it's actually not showing any warning.
OK, can you check the engine-config value for WGT? # engine-config -g GuestToolsSetupIsoPrefix
[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.
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.
This bug is in modified and targeting 4.4.1. Can we re-target to 4.4.0 and move to QE?
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.
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.