Bug 1853897 - Preserve guest agent info during live migration
Summary: Preserve guest agent info during live migration
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Core
Version: 4.50.0.13
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ovirt-4.5.1
: ---
Assignee: Tomáš Golembiovský
QA Contact: Qin Yuan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-07-05 10:26 UTC by Arik
Modified: 2022-06-23 05:54 UTC (History)
4 users (show)

Fixed In Version: vdsm-4.50.1.2
Clone Of:
Environment:
Last Closed: 2022-06-23 05:54:58 UTC
oVirt Team: Virt
Embargoed:
pm-rhel: ovirt-4.5?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github oVirt vdsm pull 191 0 None open virt: store some guest stats during migration 2022-05-19 10:35:04 UTC

Description Arik 2020-07-05 10:26:50 UTC
We've noticed that guest agent data is cleared during live VM-migration and discussed ways to prevent this as part of bz 1851726.

ovirt-engine should keep reporting the last guest agent information for a VM that is being migrated until the destination host manages to connect to qemu guest agent.

Comment 1 Arik 2021-08-29 16:38:26 UTC
Apparently it still happens despite recent improvements

Comment 2 Arik 2022-04-13 08:54:56 UTC
Tomas, we talked about this one several times before but is it something that we still want to look into?

Comment 3 Tomáš Golembiovský 2022-04-14 10:08:08 UTC
I still plan to look into it to at least asses the difficulty of it. But since it is just something nice to have the priority is really low.

Comment 4 Tomáš Golembiovský 2022-05-19 10:35:05 UTC
Not all statistics are stored. Only name of logged in user, hostname and network interface statistics are preserved. As before, other guest information will be required from the guest after migration as soon as possible.

Comment 5 Arik 2022-05-23 16:57:48 UTC
Tomas, the doc text seems to describe the fix for bz 2077008, no? :)

Comment 6 Tomáš Golembiovský 2022-05-23 17:44:43 UTC
Ah right, my bad. :)

Comment 8 Sandro Bonazzola 2022-06-23 05:54:58 UTC
This bugzilla is included in oVirt 4.5.1 release, published on June 22nd 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.1 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.


Note You need to log in before you can comment on or make changes to this bug.