Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
From: keith.wall@gmail.com
Content-Type: multipart/alternative;
	boundary=Apple-Mail-1E158924-AF66-4CEF-B6DC-D3C20F0600FD
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Subject: Re: Name resolution issue on ubuntu jenkins slaves?
Message-Id: <3AAFF0C7-449C-4555-9284-4B6B7E5543CE@gmail.com>
Date: Tue, 18 Aug 2015 22:49:46 +0100
References: 
 <CAFEMS4vhHvVeLqPoZtno32a283=KEJsf-V6rLtJFAsfqtO8T0A@mail.gmail.com>
In-Reply-To: 
 <CAFEMS4vhHvVeLqPoZtno32a283=KEJsf-V6rLtJFAsfqtO8T0A@mail.gmail.com>
To: "keith.wall@gmail.com" <keith.wall@gmail.com>,
 "builds@apache.org" <builds@apache.org>

--Apple-Mail-1E158924-AF66-4CEF-B6DC-D3C20F0600FD
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Hi Builds

Would someone be able the comment in the issue I describe below please?

--
Keith.

> On 10 Aug 2015, at 13:59, Keith W <keith.wall@gmail.com> wrote:
>=20
> Hello Apache builds,
>=20
> We (Apache Qpid) have been seeing a test fail on the Ubuntu Jenkins slaves=
 since August 9th.  The test verifies the behaviour of the code when the use=
r specifies a hostname that does not exist in DNS.  For this purpose, the te=
st uses a random name 'hg3sgaaw4lgihjs' (without hierarchal part) which is a=
ssumed not resolve.  This test is longstanding and has been running on the s=
laves for many years without issue.
>=20
> Between August 9th and 10th, something appears to have changed on the slav=
es, which is meaning that the lookup of the name is now returning an IP.  Th=
is is causing the Java test to fail. I've investigated by introducing shell c=
ommands into the job, and can see evidence of the same problem at the UNIX l=
evel.  I am certainly seeing this on slaves ubuntu4 through ubuntu6.
>=20
>=20
> $ host hg3sgaaw4lgihjs
> hg3sgaaw4lgihjs has address 198.105.244.11
> hg3sgaaw4lgihjs has address 198.105.254.11
> Host hg3sgaaw4lgihjs not found: 3(NXDOMAIN)
>=20
> $ host hg3sgaaw4lgihjs2
> hg3sgaaw4lgihjs2 has address 198.105.244.11
> hg3sgaaw4lgihjs2 has address 198.105.254.11
> Host hg3sgaaw4lgihjs2 not found: 3(NXDOMAIN)
>=20
>=20
> I considered changing the test to use a RFC-2606 Reserved Top Level DNS Na=
mes  hg3sgaaw4lgihjs.invalid but I notice that it too is resolving to 198.10=
5.244.11 too.  The fact that an .invalid address is resolving makes me suspe=
ct there is an environmental problem at the root cause.
>=20
> host hg3sgaaw4lgihjs.invalid
> hg3sgaaw4lgihjs.invalid has address 198.105.244.11
> hg3sgaaw4lgihjs.invalid has address 198.105.254.11
> Host hg3sgaaw4lgihjs.invalid not found: 3(NXDOMAIN)
>=20
> Is there a name resolution issue affecting these hosts?
>=20
> Example job affected by the issue:
>=20
> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Java-Java-Test-JDK1.=
8/
>=20
> Kind regards, Keith Wall.

--Apple-Mail-1E158924-AF66-4CEF-B6DC-D3C20F0600FD--