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:
When do migration, if I do not open 40000-50000 port on iptable, migration will fail with an error: operation failed: migration job: unexpectedly failed

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.156.el6.x86_64
libvirt-0.8.7-17.el6.x86_64
kernel-2.6.32-130.el6.x86_64


How reproducible:
100%

Steps to Reproduce:
1. prepare 2 machines and make sure selinux is enforcing and itables is running
2. run # service libvirtd restart
on both sides
3. run # setsebool virt_use_nfs 1
on both sides 
4. run #mount 10.66.90.121:/vol/S3/libvirtauto /mnt/ 
on both sides
5. define and start a domain which using the img on /mnt
6. do migration with 
# virsh migrate --live domain_name qemu+ssh://{dest ip}/system
  
Actual results:
error: operation failed: migration job: unexpectedly failed

Expected results:
succeed with no error

Additional info:
if I add 1 rule on /etc/sysconfig/iptables with
"-A INPUT -p tcp -m multiport --dports 40000:50000 -j ACCEPT" and restart iptables and libvirtd, then do migration will succeed.

Hm, is there a specific question?  This is indeed the case, and is one of the downsides of the libvirt migration code.

The good news is that this limitation is removed when using tunneled migration, and tunneled migration has other benefits.  I think this should just be a release note.

Chris Lalancette

You must open the correct ports with iptables for non-tunneled migration to succeed.  There is a separate BZ open to provide a better error message in the case of migration failure, so I'm just closing this one as not a bug.