Description of problem: Windows VM is showing the New guest tools mark even in case that the latest RHV tool is installed and the iso is located on Data Domain. Version-Release number of selected component (if applicable): ovirt-engine-tools-4.3.3.7-0.1.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Windows with older version of agent installed 2. Update RHV guest tool to the latest version 3. The New guest tools mark even after VM reboot Actual results: New guest tools mark Expected results: Not sure, i read https://bugzilla.redhat.com/show_bug.cgi?id=1612945 but i am still confused if RHV guest tool can be located on Data Domain or not. But customers are using it in this way .... Additional info: I tried to inject code with byteman to see if maybeUpdateOvirtGuestAgentStatus will be involved but comparison it works only in case of ISO domain RULE trace changed Values CLASS org.ovirt.engine.core.bll.VmHandler METHOD maybeUpdateOvirtGuestAgentStatus IF TRUE AT LINE 1001 DO traceln("The tools version " + $toolsVersion); traceStack(); ENDRULE So question ... is this expected behavior and RHV guest agent should be still on ISO domain ? Thanks !
Windows version?
So far i tested Win7, Win10 and Win10 and it's reproducible on all of them, ovirt_guest_agent_status stays 2 If i connect ISO domain with the same latest version of ISO, the ovirt_guest_agent_status moves to 1.
Sry Win7, Win10 and Win2016
it needs to be fixed and make work on any data domain. Also the autoattach (in RunVm command) should be fixed. It also looks just at the ISO domain currently.
Why target milestone oVirt 4.4.0? This is IMHO a regression introduced by the deprecation of the ISO domain in oVirt 4.3.0...
sync2jira
does this also fix bug 173053?8
bug 1730538
No, this bug is related to check if a newer version is found. While there is a comparison in both bugs this was the first patch of the two. It will be needed to rebase on top of bug 1730538 to get the right naming comparison. So it is right to say that bug 1730538 will fix the broken comparison and let auto-attach the WGT. This bug will fix the status monitoring to include data domains.
(In reply to Liran Rotenberg from comment #10) > So it is right to say that bug 1730538 will fix the broken comparison and > let auto-attach the WGT. lack of autoattachment is only relevant in oVirt, in RHV the problem is quite the opposite, always attached because of the wrong comparison. But no problem with ISO naming
WARN: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops: Bug status (ON_QA) wasn't changed but the folowing should be fixed: [Found non-acked flags: '{}', ] For more info please contact: rhv-devops
Verified on ovirt-engine-4.4.0-0.17.master.el7.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:3247