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.
