Bug 1853897
| Summary: | Preserve guest agent info during live migration | ||
|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | Arik <ahadas> |
| Component: | Core | Assignee: | Tomáš Golembiovský <tgolembi> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Qin Yuan <qiyuan> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.50.0.13 | CC: | bugs, dfodor, mburman, tgolembi |
| Target Milestone: | ovirt-4.5.1 | Keywords: | Reopened |
| Target Release: | --- | Flags: | pm-rhel:
ovirt-4.5?
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | vdsm-4.50.1.2 | Doc Type: | Bug Fix |
| Doc Text: |
Normally, the guest agent information provided by engine was not available during live migration because it was cleared. This sometimes caused issues to automation because information was unavailable until migration finished and destination vdsm connected to the guest agent. To bridge this gap some information from source vdsm is preserved during live migration, namely: logged in users, host name and network interfaces.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-06-23 05:54:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Arik
2020-07-05 10:26:50 UTC
Apparently it still happens despite recent improvements Tomas, we talked about this one several times before but is it something that we still want to look into? 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. 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. Tomas, the doc text seems to describe the fix for bz 2077008, no? :) Ah right, my bad. :) 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. |