Bug 681109

Summary: Migration fail error is vague when don't set #iptables -F
Product: Red Hat Enterprise Linux 6 Reporter: zhanghaiyan <yoyzhang>
Component: libvirtAssignee: Daniel Veillard <veillard>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: dallan, dyuan, eblake, llim, weizhan, xen-maint
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-10 02:28:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description zhanghaiyan 2011-03-01 06:09:02 UTC 
Description of problem:
Migration fail error is vague when don't set #iptables -F

Version-Release number of selected component (if applicable):
- kernel-2.6.32-117.el6.x86_64
- qemu-kvm-0.12.1.2-2.147.el6.x86_64
- libvirt-0.8.7-8.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Set up migration environment on 2 hosts except forgetting to set #iptables -F  
2. # virsh migrate --live rhel61_i386_1 qemu+ssh://10.66.93.59/system
root.93.59's password: 
error: operation failed: migration job: unexpectedly failed
3. Set up #iptables -F on 2 hosts
# virsh migrate --live rhel61_i386_1 qemu+ssh://10.66.93.59/system
root.93.59's password: 

[root@dhcp-65-132 ~]#

Actual results:
2. the error info is rather vague

Expected results:
2. give a more clear reminding info is better

Additional info:
Comment 2 RHEL Program Management 2011-04-04 02:06:52 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 3 Dave Allan 2011-06-10 02:28:06 UTC 

*** This bug has been marked as a duplicate of bug 615941 ***