From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Jim Fehlig <jfehlig@suse.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [osstest test] 60719: tolerable FAIL - PUSHED
Date: Sat, 22 Aug 2015 08:25:48 +0100 [thread overview]
Message-ID: <1440228348.23097.36.camel@citrix.com> (raw)
In-Reply-To: <20150821140257.GA20276@zion.uk.xensource.com>
On Fri, 2015-08-21 at 15:02 +0100, Wei Liu wrote:
> 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@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
> >
> > > 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.
Whether or not it does the failure here is Invalid Argument, not
Connection Refused, so I don't think we are getting as far as that
particular failure.
Ian.
next prev parent reply other threads:[~2015-08-22 7:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <osstest-60719-mainreport@xen.org>
2015-08-21 8:05 ` [osstest test] 60719: tolerable FAIL - PUSHED Ian Campbell
2015-08-21 14:02 ` Wei Liu
2015-08-22 7:25 ` Ian Campbell [this message]
2015-08-27 3:33 ` Jim Fehlig
2015-09-01 12:47 ` Ian Jackson
2015-09-01 13:14 ` Ian Campbell
2015-09-03 6:38 ` Jim Fehlig
2015-09-03 10:26 ` Ian Campbell
2015-09-03 10:49 ` Ian Jackson
2015-09-03 10:57 ` Ian Campbell
2015-09-03 16:04 ` Ian Campbell
2015-09-03 11:37 ` Ian Campbell
2015-09-03 16:35 ` Jim Fehlig
2015-09-03 16:49 ` Ian Campbell
2015-09-10 16:40 ` Ian Campbell
2015-09-12 3:56 ` Jim Fehlig
2015-09-16 8:28 ` Ian Campbell
2015-09-04 2:47 ` Jim Fehlig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1440228348.23097.36.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=jfehlig@suse.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).