All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [osstest test] 60719: tolerable FAIL - PUSHED
Date: Thu, 3 Sep 2015 20:47:53 -0600	[thread overview]
Message-ID: <55E90659.40702@suse.com> (raw)
In-Reply-To: <21989.40565.161215.97306@mariner.uk.xensource.com>

On 09/01/2015 06:47 AM, 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_Administration_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:
>
> root@nocera0:~# host nocera1.test-lab.xenproject.org
> nocera1.test-lab.xenproject.org has address 172.16.144.23
> root@nocera0:~# host -i 172.16.144.23
> Host 23.144.16.172.in-addr.arpa. not found: 3(NXDOMAIN)
> root@nocera0:~# cat /etc/hosts
> 127.0.0.1       localhost
> 127.0.1.1       nocera0.test-lab.xenproject.org nocera0
>
> # The following lines are desirable for IPv6 capable hosts
> ::1     localhost ip6-localhost ip6-loopback
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
> root@nocera0:~# cat /etc/resolv.conf
> domain test-lab.xenproject.org
> search test-lab.xenproject.org
> nameserver 172.16.148.4
> nameserver 172.16.144.3
> root@nocera0:~#
>
> 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 ?
>
> I can probably put the test boxes in the reverse DNS, but really I
> think at the very least libvirt's error message needs to be improved
> too.

The unhelpful "Invalid argument" error has been fixed

http://libvirt.org/git/?p=libvirt.git;a=commit;h=6ce939c2472e8cd97dfe448e902bc878c826351e

Regards,
Jim

      parent reply	other threads:[~2015-09-04  2:47 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
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 [this message]

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=55E90659.40702@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.