On 08/21/2015 02:05 AM, Ian Campbell wrote:
On Wed, 2015-08-19 at 00:18 +0000, osstest service owner wrote:
flight 60719 osstest real [real]
http://logs.test-lab.xenproject.org/osstest/logs/60719/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
[...]
test-amd64-i386-libvirt-pair 21 guest-migrate/src_host/dst_host fail never
pass
test-amd64-amd64-libvirt-pair 21 guest-migrate/src_host/dst_host fail never
pass
All of the pending changes are now in production, the libvirt migration
test is now failing in the production colo with:
2015-08-18 19:07:36 Z executing ssh ... root@172.16.144.34 virsh migrate --live
debian.guest.osstest xen+ssh://pinot1
error: unable to connect to 'pinot1.test-lab.xenproject.org:49152': Invalid
argument
This sounds a bit like an issue discussed in the Redhat libvirt troubleshooting
FAQ
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Deployment_and_Administration_Guide/sect-Troubleshooting-Common_libvirt_errors_and_troubleshooting.html#sect-Migration_fails_with_Error_unable_to_resolve_address
From the _controller_ pinot1.test-lab.xenproject.org is valid:
ianc@osstest :~$ ping -c 1 pinot1.test-lab.xenproject.org
PING pinot1.test-lab.xenproject.org (172.16.144.35) 56(84) bytes of data.
64 bytes from 172.16.144.35: icmp_req=1 ttl=64 time=0.258 ms
--- pinot1.test-lab.xenproject.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.258/0.258/0.258/0.000 ms
Maybe the test boxes are seeing a different view of DNS, but I doubt
it. Also I note that the failure is "Invalid argument" and not "Unknown
host".
Right. If it is a DNS issue, error handling in the libvirt libxl migration code
needs improving.
Regards,
Jim
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
