+++ This bug was initially created as a clone of Bug #1883875 +++ Description of problem: After some period of time, guest agent data stops being reported by virtctl, even though the guest agent is active. The exact threshold at which the data stops being reported is unknown. Version-Release number of selected component (if applicable): virtctl client v0.33.0 How reproducible: 100% Steps to Reproduce: 1. Create and start a VM or VMI 2. Install and enable the guest agent 3. Let it run for potentially up to 24 hours 4. Request the guestosinfo from virtctl Actual results: An error is displayed Expected results: The guestosinfo details are displayed Additional info: This is the error that I get: virtctl -n rhodes guestosinfo vmi-fedora {"component":"","level":"error","msg":"Cannot retrieve GuestOSInfo: an error on the server (\"Operation cannot be fulfilled on virtualmachineinstance.kubevirt.io \\\"vmi-fedora\\\": VMI does not have guest agent connected\") has prevented the request from succeeding","pos":"vmi.go:449","timestamp":"2020-09-30T12:11:56.369648Z"} Error getting guestosinfo of VirtualMachine vmi-fedora, an error on the server ("Operation cannot be fulfilled on virtualmachineinstance.kubevirt.io \"vmi-fedora\": VMI does not have guest agent connected") has prevented the request from succeeding --- Additional comment from Nelly Credi on 2020-09-30 15:45:29 UTC --- based on the virtctl version indicated, im setting the bug version to 2.5 instead of 2.1 --- Additional comment from on 2020-09-30 16:10:42 UTC --- Actually, it's important to clarify that. Phillip, what version of CNV is running on your cluster? The description of this BZ makes it sound like it might be related to these BZs: https://bugzilla.redhat.com/show_bug.cgi?id=1847525 https://bugzilla.redhat.com/show_bug.cgi?id=1856979 --- Additional comment from Kedar Bidarkar on 2020-11-19 14:53:08 UTC --- We suspect this is a duplicate of this bug https://bugzilla.redhat.com/show_bug.cgi?id=1883875 --- Additional comment from Kedar Bidarkar on 2020-11-19 14:53:34 UTC --- Ignore comment 3 We suspect this is a duplicate of this bug https://bugzilla.redhat.com/show_bug.cgi?id=1886453 --- Additional comment from Fabian Deutsch on 2020-11-19 19:35:52 UTC --- This is probably seen by Ford. --- Additional comment from Israel Pinto on 2021-02-02 11:49:36 UTC --- moving back to assign since: https://bugzilla.redhat.com/show_bug.cgi?id=1886453#c17 --- Additional comment from Shaul Garbourg on 2021-02-04 10:45:45 UTC --- The following steps were done: 1. Fedora VM was created and a guest agent was installed. 2. fslist returned the information properly. 3. Migrate the VM. 4. At the beginning (2 minutes after migration), the fslist worked and returned the information properly for the migrated VM. a few minutes later (4 mins). The fslist stopped working. Lubo is investigating the code and will update on progress --- Additional comment from on 2021-02-08 09:03:38 UTC --- Fixing the bug in https://github.com/kubevirt/kubevirt/pull/4982 --- Additional comment from on 2021-02-16 19:03:50 UTC --- PR was merged. Waiting for 2.6.0 to be released before backporting this to the stable release branch. --- Additional comment from on 2021-03-10 22:12:01 UTC --- Lubo, Can you please backport relevant PRs to the release-0.36 branch? --- Additional comment from on 2021-03-15 09:54:09 UTC --- It's almost there https://github.com/kubevirt/kubevirt/pull/5198 . --- Additional comment from on 2021-03-24 20:01:41 UTC --- Verified on hco v2.6.1-5 Followed steps: 1) create and start vm - OK 2) check guest os info (virtctl get guestosinfo/fslist/userlist) - OK 3) wait ~ 1 hour and check guest os info again - OK 4) migrate vm and check guest os info after ~ 5 hour - OK
verify with build: virt-operator-container-v2.5.6-3 hco-bundle-registry-container-v2.5.6-65 step: 1. create and start vm 2. check guest agent within vm 3. run virtctl get guestosinfo/fslist/userlist 4. wait >24 hours, run virrtctl to get guest os info again 5. migrate vm and check guest os info after 24 hours all passed without error. move to verified.
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 (OpenShift Virtualization 2.5.6 Images), 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/RHEA-2021:2045