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 non-existent xml does not report error messages although it returns non-zero value


Version-Release number of selected component (if applicable):
kernel-2.6.32-223.el6.x86_64
libvirt-0.9.9-1.el6.x86_64
qemu-kvm-0.12.1.2-2.213.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Prepare migration environment with shared nfs dir and start a guest

2. Do migration with
# virsh migrate kvm-rhel6u2-x86_64-new --live qemu+ssh://10.66.83.197/system --xml non-existent-xml
no error messages here and migration returns immediately 

3. Check return value
# echo $?
1
  
Actual results:
It does not report any error messages

Expected results:
It should report error messages

Additional info:

Patch for upstream:
https://www.redhat.com/archives/libvir-list/2012-January/msg00388.html

In POST:
commit c41a21de3abb6a080d87360ed7b246b070703b88
Author: Alex Jia <ajia>
Date:   Wed Jan 11 16:23:03 2012 +0800

    virsh: improve doMigrate function docs
    
    When running virsh migrate with --xml option and actual xml file doesn't
    exist, virsh hasn't output any error information, although return value
    is 1.
    
    * tools/virsh.c: Raising a appropriate error information when operation fails.
    
    * How to reproduce?
    % virsh migrate <domain> --live qemu+ssh://<target host>/system --xml non-existent.xml
    % echo $?
    
    * Fixed result:
    error: file 'non-existent.xml' doesn't exist
    
    Signed-off-by: Alex Jia <ajia>

Verify pass on 
libvirt-0.9.10-1.el6.x86_64
qemu-kvm-0.12.1.2-2.225.el6.x86_64
kernel-2.6.32-230.el6.x86_64

# virsh migrate --live tt qemu+ssh://10.66.85.218/system --xml none-exist.xml
error: file 'none-exist.xml' doesn't exist

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/RHSA-2012-0748.html