Re: [Xen-devel] [osstest test] 60719: tolerable FAIL - PUSHED

[Wei Liu <wei.liu2@xxxxxxxxxx>]

On Fri, Aug 21, 2015 at 09:05:30AM +0100, 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@xxxxxxxxxxxxx virsh migrate 
> --live debian.guest.osstest xen+ssh://pinot1
> error: unable to connect to 'pinot1.test-lab.xenproject.org:49152': Invalid 
> argument
> 
> >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".
> 
> Anyone got any idea what is going on?
> 

I notice that libvirtd is not configured to listen to tcp connection,
while tls connection is enabled by default.

# This is disabled by default, uncomment this to enable it.
#listen_tcp = 1


# This is enabled by default, uncomment this to disable it
#listen_tls = 0

I'm not sure if xen+ssh:// requires enabling listen_tcp.

Wei.



> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel