Following BZ 1936298 After upgrading the guest-agent on Windows VM, the mark wasn't updated as it was expected. It happens when ISO domain is active. If there is no active ISO domain, it will be updated in 3 minutes intervals. We may consider to detect the change in the VM applist and then call the check of the guest-agent version and update the mark if needed.
The steps to reproduce (coming from Petr's bug): 1. create a windows vm. 2. install old virtio-win drivers (having not the latest guest-agent). 3. have the newer virtio-win installed, iso exists on iso domain (if needed, trigger it by refreshing the iso, for example editing a vm and closing the edit popup). 4. see you have the mark that newer guest-agent available. 5. update the windows vm guest-agent. 6. (optional) you may require to reboot the vm in order to have it proper installed in the OS. 7. once the vm is up and reports the new version it suppose of guest agent(latest available), do nothing and wait. expected results: in step 7, after awhile the mark should be gone. real result: the mark stays until you trigger iso refresh (can be triggered by multiple flows).
no update for a while, didn't make it into 4.5, closing
Should be a relatively easy fix. As we didn't provide a good alternative for ISO domains, we should assume they would still exist - and if we can easily improve this flow, I think we should
This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).
This bug has low overall severity and passed an automated regression suite, and is not going to be further verified by QE. If you believe special care is required, feel free to re-open to ON_QA status.