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.
Description of problem:
migration with --dname will fail with error
# virsh migrate --live kvm-rhel6-x86_64 qemu+ssh://10.66.83.178/system --dname kvm-rhel6-x86_64-new
error: internal error Incoming cookie data had unexpected name kvm-rhel6-x86_64 vs kvm-rhel6-x86_64-new
And on target host, it has a transient domain which named kvm-rhel6-x86_64-new transient domain in shut off status.
it can succeed on rhel6.1 libvirt-0.8.7.18, so it is a regression bug
Version-Release number of selected component (if applicable):
kernel-2.6.32-197.el6.x86_64
qemu-kvm-0.12.1.2-2.192.el6.x86_64
libvirt-0.9.4-12.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. Prepare 2 hosts and prepare a nfs which is mounted on both hosts, and setting the virt_use_nfs boolean on both sides
# setsebool virt_use_nfs 1
and close the iptable on both sides
# iptables -F
2. Do migration
# virsh migrate --live kvm-rhel6-x86_64 qemu+ssh://10.66.83.178/system --dname kvm-rhel6-x86_64-new
Actual results:
error:internal error Incoming cookie data had unexpected name kvm-rhel6-x86_64 vs kvm-rhel6-x86_64-new
Expected results:
succeed with no error
Additional info:
Oh, migration cookie handling was enhanced in a way that is incompatible with dname. We send domain name as part of migration cookie and check that the name matches when parsing the cookie. However, source libvirtd sends old name in the cookie and destination libvirtd expects to see the new name there because it is always taken from the domain object. Fixing this would require explicitly passing name of the domain to functions that handle migration cookies.
This is fixed upstream by
commit cdd5ef7b0776c5fa09a1b5bcb5d8adbc82b525bd
Author: Jiri Denemark <jdenemar>
Date: Tue Oct 4 09:11:35 2011 +0200
qemu: Fix migration with dname
Destination libvirtd remembers the original name in the prepare phase
and clears it in the finish phase. The original name is used when
comparing domain name in migration cookie.
verify pass on
libvirt-0.9.4-16.el6.x86_64
kernel-2.6.32-206.el6.x86_64
qemu-kvm-0.12.1.2-2.195.el6.x86_64
with --dname, there is no error on migration.
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.
http://rhn.redhat.com/errata/RHBA-2011-1513.html