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.
Bug 1442705 - Migration job is not active when migrating guest from target host to source host
Summary: Migration job is not active when migrating guest from target host to source ...
Keywords:
Status: CLOSED DUPLICATE of bug 1441165
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Jiri Denemark
QA Contact: zhe peng
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-17 08:08 UTC by Dan Zheng
Modified: 2017-04-18 10:03 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-18 10:03:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
libvirt log on source host (9.34 MB, text/plain)
2017-04-17 08:08 UTC, Dan Zheng
no flags Details
libvirtd log on target host (6.52 MB, text/plain)
2017-04-17 08:11 UTC, Dan Zheng
no flags Details
qemu log on target (673.14 KB, text/plain)
2017-04-17 08:24 UTC, Dan Zheng
no flags Details
qemu log on source (1.09 MB, text/plain)
2017-04-17 08:35 UTC, Dan Zheng
no flags Details

Description Dan Zheng 2017-04-17 08:08:43 UTC
Created attachment 1271998 [details]
libvirt log on source host

Description of problem:
The migaration job works normal from source to target, but fails from target to host.

Version-Release number of selected component (if applicable):
libvirt-3.2.0-2.el7.x86_64
qemu-kvm-rhev-2.8.0-6.el7.x86_64
kernel-3.10.0-574.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Setup nfs environment and start a guest
2. Run migration command on source host:
virsh  migrate rhel7 --live --p2p --verbose --unsafe qemu+ssh://<target_host>:22/system
Migration: [100 %]
3. Run list command on target host:
# virsh list --all
 Id    Name                           State
----------------------------------------------------
 2     rhel7                          running
4. Run migration commmand on target host:
# virsh  migrate rhel7 --live --p2p --verbose qemu+ssh://<source_host>:22/system
error: operation failed: migration job: is not active

Actual results:
See above

Expected results:
Migration should be successful.

Additional info:
See logs in attachments.

Comment 2 Dan Zheng 2017-04-17 08:11:19 UTC
Created attachment 1271999 [details]
libvirtd log on target host

Comment 3 Dan Zheng 2017-04-17 08:24:30 UTC
Created attachment 1272000 [details]
qemu log on target

Comment 4 Dan Zheng 2017-04-17 08:35:31 UTC
Created attachment 1272003 [details]
qemu log on source


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