xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>, Jim Fehlig <jfehlig@suse.com>
Cc: Wei Liu <wei.liu2@citrix.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [osstest test] 60719: tolerable FAIL - PUSHED
Date: Tue, 1 Sep 2015 14:14:49 +0100	[thread overview]
Message-ID: <1441113289.26292.8.camel@citrix.com> (raw)
In-Reply-To: <21989.40565.161215.97306@mariner.uk.xensource.com>

On Tue, 2015-09-01 at 13:47 +0100, Ian Jackson wrote:
> Jim Fehlig writes ("Re: [osstest test] 60719: tolerable FAIL - PUSHED"):
> > 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_Admin
> > istration_Guide/sect-Troubleshooting
> > -Common_libvirt_errors_and_troubleshooting.html#sect
> > -Migration_fails_with_Error_unable_to_resolve_address
> 
> > Right. If it is a DNS issue, error handling in the libvirt libxl
> > migration code needs improving.
> 
> I booked out a test host, and (as I expected) forward DNS works, but
> reverse DNS on test box IP addresses does not:

As discussed IRL I was also investigating this using the Cambridge
instance, which does have correct reverse DNS:

    root@moss-bug    :~# host moss-bug.xs.citrite.net
    moss-bug.xs.citrite.net has address 10.80.229.144
    root@moss-bug    :~# host -i 10.80.229.144
    144.229.80.10.in-addr.arpa domain name pointer moss-bug.xs.citrite.net.
    root@moss-bug    :~# domainname -f
    moss-bug.xs.citrite.net
    root@moss-bug    :~# cat /etc/hosts
    127.0.0.1    	    localhost
    127.0.1.1    	    moss-bug.xs.citrite.net    	    moss-bug

    # The following lines are desirable for IPv6 capable hosts
    ::1     localhost ip6-localhost ip6-loopback
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters
    root@moss-bug    :~#

(previously these machines had a wrong idea about their own FQDN, that is
now fixed)

I am now seeing the same error as the production instance:

2015-09-01 12:10:00 Z executing ssh ... root@10.80.229.144 virsh --debug 0 migrate --live debian.guest.osstest xen+ssh://10.80.228.77
migrate: live(bool): (none)
migrate: domain(optdata): debian.guest.osstest
migrate: desturi(optdata): xen+ssh://10.80.228.77
migrate: found option <domain>: debian.guest.osstest
migrate: <domain> trying as domain NAME
migrate: found option <domain>: debian.guest.osstest
migrate: <domain> trying as domain NAME
error: unable to connect to 'lace-bug.xs.citrite.net:49152': Invalid argument

> That admin guide article isn't quite clear, but reading between the
> lines and applying some supposition, maybe libvirt is doing a reverse
> lookup on some associated IP address ?

Based on the above that doesn't seem to be the case. So...

> I can probably put the test boxes in the reverse DNS,

... this is probably not needed.

>  but really I
> think at the very least libvirt's error message needs to be improved
> too.

Ian.

  reply	other threads:[~2015-09-01 13:14 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
2015-09-01 12:47     ` Ian Jackson
2015-09-01 13:14       ` Ian Campbell [this message]
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=1441113289.26292.8.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).