All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: Ian Campbell <ian.campbell@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [osstest test] 60719: tolerable FAIL - PUSHED
Date: Wed, 26 Aug 2015 21:33:39 -0600	[thread overview]
Message-ID: <55DE8513.3000205@suse.com> (raw)
In-Reply-To: <1440144330.19360.4.camel@citrix.com>

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

  parent reply	other threads:[~2015-08-27  3:33 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
2015-08-27  3:33   ` Jim Fehlig [this message]
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=55DE8513.3000205@suse.com \
    --to=jfehlig@suse.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=ian.campbell@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.