Bug 1457052
| Summary: | "Unknown" operation is reported in domain job stats on the target host after migration | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | yafu <yafu> |
| Component: | libvirt | Assignee: | Jiri Denemark <jdenemar> |
| Status: | CLOSED ERRATA | QA Contact: | chenruping <ruchen> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | dyuan, dzheng, fjin, lizhu, rbalakri, xuzhang, yanqzhan, zpeng |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | libvirt-3.2.0-9.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-08-02 01:34:35 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
yafu
2017-05-31 03:10:35 UTC
Patch sent upstream for review: https://www.redhat.com/archives/libvir-list/2017-June/msg00220.html Fixed upstream by
commit 49d30bc2e292785bf2edc121c12bc5c10264d1d4
Refs: v3.4.0-36-g49d30bc2e
Author: Jiri Denemark <jdenemar>
AuthorDate: Wed May 31 10:08:28 2017 +0200
Commit: Jiri Denemark <jdenemar>
CommitDate: Wed Jun 7 09:14:02 2017 +0200
qemu: Set operation on completed migration job
Without this patch libvirt would just report the operation of a
completed job as "unknown" instead of "incoming migration".
https://bugzilla.redhat.com/show_bug.cgi?id=1457052
Signed-off-by: Jiri Denemark <jdenemar>
I can reproduce the bug with build: libvirt-3.2.0-6.virtcov.el7.x86_64 Verified pass with Qemu-kvm-rhev-2.9.0-10.el7.x86_64 Libvirt-3.2.0-10.virtcov.el7.x86_64 Test steps: 1.Do migration # virsh migrate rhel72 qemu+ssh://10.66.69.11/system --live --verbose Migration: [100 %] 2.After migration complete, execute 'virsh domjobinfo domain --completed' 2.1.on the target host: # virsh domjobinfo rhel72 --completed Job type: Completed Operation: Incoming migration Time elapsed: 305724 ms Time elapsed w/o network: 272858 ms Data processed: 795.407 MiB Data remaining: 0.000 B Data total: 1.126 GiB Memory processed: 795.407 MiB Memory remaining: 0.000 B Memory total: 1.126 GiB Memory bandwidth: 2.929 MiB/s Dirty rate: 0 pages/s Iteration: 7 Constant pages: 132313 Normal pages: 202936 Normal data: 792.719 MiB Total downtime: 34726 ms Downtime w/o network: 1860 ms Setup time: 68 ms 2.2.On the source host ： # virsh domjobinfo rhel72 --completed Job type: Completed Operation: Outgoing migration Time elapsed: 273029 ms Time elapsed w/o network: 240163 ms Data processed: 795.407 MiB Data remaining: 0.000 B Data total: 1.126 GiB Memory processed: 795.407 MiB Memory remaining: 0.000 B Memory total: 1.126 GiB Memory bandwidth: 2.929 MiB/s Dirty rate: 0 pages/s Iteration: 7 Constant pages: 132313 Normal pages: 202936 Normal data: 792.719 MiB Total downtime: 34726 ms Downtime w/o network: 1860 ms Setup time: 68 ms According to the test results above, move the bug 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, 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-2017:1846 |