Re: [Xen-devel] [PATCH OSSTEST] ts-xen-install: Install netcat-openbsd

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Thu, 2015-08-13 at 14:59 +0100, Ian Campbell wrote:
> On Thu, 2015-08-13 at 11:38 +0100, Ian Campbell wrote:
> > Lets see if "virsh --debug 0" tells me anything
> 
> http://xenbits.xen.org/people/ianc/tmp/37833/
> 
> 2015-08-13 13:02:39 Z executing ssh ... root@xxxxxxxxxxxxx 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.uk.xensource.com:49152': Invalid 
> argument
> 
> So I'm no wiser...
> 
> I grabbed the box in this state and a simple "ssh lace-bug" (AKA
> 10.80.228.77) just worked.
> 
> The host has:
> 
> # cat /etc/resolv.conf 
> domain uk.xensource.com
> search uk.xensource.com. xensource.com. xs.citrite.net. eng.citrite.net. 
> citrite.net.
> nameserver 10.80.16.125
> nameserver 10.80.16.126
> #
> 
> Which I guess explains to some extent where lace-bug.uk.xensource.com is
> coming from in the xen+ssh://lace-bug case (sort of) but not really for 
> the
> xen+ssh://lace-bug.xs.citrite.net nor xen+ssh://10.80.228.77 cases.

I've just spotted (on moss-bug, lace-bug has equivalent):

    # cat /etc/hosts
    127.0.0.1               localhost
    127.0.1.1               moss-bug.uk.xensource.com               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
    # cat /var/lib/dhcp/dhclient.eth0.leases 
    lease {
      interface "eth0";
      fixed-address 10.80.229.144;
      filename "/pxelinux.0";
      option subnet-mask 255.255.240.0;
      option routers 10.80.224.1;
      option dhcp-lease-time 43200;
      option dhcp-message-type 5;
      option domain-name-servers 10.80.16.125,10.80.16.126;
      option dhcp-server-identifier 10.80.16.125;
      option domain-search "uk.xensource.com.", "xensource.com.", 
"xs.citrite.net.", "eng.citrite.net.", "citrite.net.";
      option ntp-servers 10.80.16.80,10.80.248.8;
      option host-name "moss-bug";
      option domain-name "uk.xensource.com";
      renew 4 2015/08/13 17:38:48;
      rebind 4 2015/08/13 23:19:23;
      expire 5 2015/08/14 00:49:23;
    }
    # domainname 
    (none)
    # hostname -f
    moss-bug.uk.xensource.com

I think /etc/hosts came from the installer getting the same domain-name
option in DHCP as shown above.

So I think that is a local infrastructure bug (which I'll get fixed) but I
also think that virsh's behaviour when given a FQDN or an explicit IP
address is strange.

> 
> Jim, do you have any idea what is going on or who/what is doing this
> translation?
> 
> This is all on the Cambridge instance of osstest, the XenProject instance
> in the colo has only a single domain name, so things may work as they are
> today (once the right version of netcat is added), but I'd still like to
> get to the bottom of it, since it'll affect other people I'm sure.
> 
> Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel