Description of problem: When guest agent stops reporting information for some interface the engine still caches the data and reports it to the user. The 'IP address' column in 'Virtual Machines' view is updated properly, but the 'Network' section and 'Guest Agent data' subsection in the VM details view still reports the original data. The data returned by REST API also report the old data Is this the intended behaviour or a bug? Note that we have an RFE for guest agent (bug 1437145) to disable reporting of specific network interfaces. When the disabled interface is eth0 engine still reports the data even though guest agent is not reporting it any more.
It's intentional to cache IP. However we do not have to cache the whole interface and when it disappears the data should be cleared
Tomas, was there any NIC keep being reported by the guest agent?
I retested this and it seems the problem exists only when you blacklist all the NICs. As long as at least one NIC is reported from guest agent the cached data are cleared properly.
In light of comment 3, this should be fixed on the master branch already.
Arik, i think that on VM shutdown the IP addresses should be returned to N/A as well.
Except the shutdown flow i think this can be verified. When stopping the guest-agent(qemu/ovirt) on the VM, the IP addresses are gone from the column and from the network interfaces sub tab. which is ok. But i truly believe that shut down VM should behave the same, if no guest agent is running, the IP address should be N/A on the network interface sub tab. Let me know what you think, Tested on - 4.3.0-0.0.master.20180819104048.git932969e.el7
(In reply to Michael Burman from comment #5) > Arik, i think that on VM shutdown the IP addresses should be returned to N/A > as well. Well, could be but should be discussed separately.
Verified on - 4.3.0-0.0.master.20180819104048.git932969e.el7 For the shut down VM scenario i reported this - BZ 1619534 The same behavior should be when shutting down the VM
This bugzilla is included in oVirt 4.2.7 release, published on November 2nd 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.7 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.
Closed by mistake, moving back to qa -> verified
This bugzilla is included in oVirt 4.3.0 release, published on February 4th 2019. Since the problem described in this bug report should be resolved in oVirt 4.3.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.