Bug 1320500

Summary: migration from RHEL6.8 to RHEL7.3 host failed with error "Unsupported migration cookie feature persistent"
Product: Red Hat Enterprise Linux 7 Reporter: yafu <yafu>
Component: libvirtAssignee: Jiri Denemark <jdenemar>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: dgilbert, dyuan, fjin, mzhan, rbalakri, zhanghm.zhm, zhanghongming, zpeng
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: libvirt-2.0.0-3.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-03 18:40:31 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:
Attachments:
Description Flags
libvirtd.log none

Description yafu 2016-03-23 10:56:49 UTC
Created attachment 1139508 [details]
libvirtd.log

Description of problem:
migration from RHEL6.8 to RHEL7.3 host failed with error "Unsupported migration cookie feature persistent"

Version-Release number of selected component (if applicable):
rhel6.8:
libvirt-0.10.2-59.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.490.el6.x86_64

rhel7.3:
libvirt-1.3.2-1.el7.x86_64
qemu-kvm-rhev-2.3.0-31.el7.x86_64


How reproducible:
100%

steps to reproduce:
1.Do migration from rhel6.8 to rhel7.3:
 #virsh migrate qemu+ssh://10.73.196.125/system --live --verbose
  root.196.125's password:
 Migration: [ 98 %]error: internal error: Unsupported migration cookie feature persistent

2.Check the libvirtd's log on target host:
 #cat /var/log/libvirt/libvirtd.log | grep -i "Unsupported migration cookie feature persistent"
  error : qemuMigrationCookieXMLParse:1250 : internal error: Unsupported migration cookie feature persistent


Actual results:
Migration from RHEL6.8 to RHEL7.3 failed with error "Unsupported migration cookie feature persistent"

Expected results:
Migration from RHEL6.8 to RHEL7.3 should be complete correctly.

Additional info:
1.Migration from rhel6.8 to rhel7.2 can be complete correctly.
2.The "Unsupported migration cookie feature persistent" is a result of a bug on RHEL-6 libvirt, which sends persistent XML in the cookie even though VIR_MIGRATE_PERSIST_DEST was not used. But this is harmless. So maybe the rhel7.3 needs to be compatible with it.

Comment 1 Dr. David Alan Gilbert 2016-06-09 18:02:26 UTC
Yeh can confirm; just hit the same thing libvirt-0.10.2-60.el6.x86_64->libvirt-1.3.5-1.el7.x86_64

(It does work if I use --persistent on the migrate).

Dave

Comment 2 Jiri Denemark 2016-07-18 13:11:15 UTC
Patch sent upstream for review: https://www.redhat.com/archives/libvir-list/2016-July/msg00638.html

Comment 3 Jiri Denemark 2016-07-18 15:37:43 UTC
Fixed upstream by

commit 338f772e923ce07148abe6dcaf3d62b744e7baf5
Refs: v2.0.0-165-g338f772
Author:     Jiri Denemark <jdenemar>
AuthorDate: Mon Jul 18 13:17:28 2016 +0200
Commit:     Jiri Denemark <jdenemar>
CommitDate: Mon Jul 18 17:38:03 2016 +0200

    qemu: Fix migration from old libvirt

    Older libvirt versions send persistent XML in a migration cookie even
    when VIR_MIGRATE_PERSIST_DEST flag is not used, but current libvirt
    properly fails if the cookie contains unexpected flags. Thus migration
    from old libvirt fails with

        internal error: Unsupported migration cookie feature persistent

    unless VIR_MIGRATE_PERSIST_DEST flag is set.

    https://bugzilla.redhat.com/show_bug.cgi?id=1320500

    Signed-off-by: Jiri Denemark <jdenemar>

Comment 6 Fangge Jin 2016-08-09 05:53:39 UTC
I can reproduce this BZ on build:
RHEL6.8:
libvirt-0.10.2-59.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.491.el6.x86_64

RHEL7.3:
libvirt-2.0.0-2.el7.x86_64
qemu-kvm-rhev-2.6.0-18.el7.x86_64


Verify this BZ on build:
RHEL7.3:
libvirt-2.0.0-4.el7.x86_64
qemu-kvm-rhev-2.6.0-18.el7.x86_64

Migration succeeds and guest disappears after destroyed on target

Comment 8 errata-xmlrpc 2016-11-03 18:40:31 UTC
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://rhn.redhat.com/errata/RHSA-2016-2577.html