Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 1919951[details]
virtqemud log
Description of problem:
Check domjobinfo on target host after migration completes, the Operation field is "Unknown".
Version-Release number of selected component (if applicable):
qemu-kvm-7.1.0-3.el9.x86_64
libvirt-8.8.0-1.el9.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Start guest
2. Migrate guest to target host
# virsh migrate vm1 qemu+tcp://{taraget_host}/system --live --p2p
3. After migration completes, check domjobinfo
1) On src host:
# virsh domjobinfo vm1 --completed
Job type: Completed
Operation: Outgoing migration
Time elapsed: 7356 ms
Data processed: 620.024 MiB
...
2) On target host:
# virsh domjobinfo vm1 --completed
Job type: Completed
Operation: Unknown
Time elapsed: 7349 ms
Data processed: 620.024 MiB
Actual results:
The "Operation" field of domjobinfo of target host is "Unknown"
Expected results:
The "Operation" field of domjobinfo of target host should be "Incoming migration"
Additional info:
This is now fixed upstream by
commit af59c944bb36f11996d03069116df2f14d7a8136
Refs: v8.10.0-rc2-9-gaf59c944bb
Author: Jiri Denemark <jdenemar>
AuthorDate: Wed Nov 30 14:29:55 2022 +0100
Commit: Jiri Denemark <jdenemar>
CommitDate: Thu Dec 1 10:30:21 2022 +0100
qemu: Pass vm to qemuMigrationCookieParse if it exists
The vm object is used inside qemuMigrationCookieParse based on the flags
passed to qemuMigrationCookieParse and the content of the cookie. The
callers should not just blindly guess and pass NULL if they
(incorrectly) think the vm object is not needed. We should always pass
the vm object unless it does not exist yet.
This fixes a bug when statistics of a completed migration reported
"Unknown" operation instead of "Incoming migration" on the destination
host.
https://bugzilla.redhat.com/show_bug.cgi?id=2137298
Fixes: v8.7.0-79-g0150f7a8c1
Signed-off-by: Jiri Denemark <jdenemar>
Reviewed-by: Michal Privoznik <mprivozn>
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 (libvirt bug fix and enhancement update), 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/RHBA-2023:2171
Created attachment 1919951 [details] virtqemud log Description of problem: Check domjobinfo on target host after migration completes, the Operation field is "Unknown". Version-Release number of selected component (if applicable): qemu-kvm-7.1.0-3.el9.x86_64 libvirt-8.8.0-1.el9.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start guest 2. Migrate guest to target host # virsh migrate vm1 qemu+tcp://{taraget_host}/system --live --p2p 3. After migration completes, check domjobinfo 1) On src host: # virsh domjobinfo vm1 --completed Job type: Completed Operation: Outgoing migration Time elapsed: 7356 ms Data processed: 620.024 MiB ... 2) On target host: # virsh domjobinfo vm1 --completed Job type: Completed Operation: Unknown Time elapsed: 7349 ms Data processed: 620.024 MiB Actual results: The "Operation" field of domjobinfo of target host is "Unknown" Expected results: The "Operation" field of domjobinfo of target host should be "Incoming migration" Additional info: