dnsmasq resolves fuel.domain.tld to 127.0.0.1 due to faulty hosts entries on fuel server

[Christian Huebner]

On the fuel server in /etc/hosts multiple entries for fuel.domain.tld resolve this name to 127.0.0.1

This is propagated by dnsmasq, leading to the clients also resolving fuel.domain.tld to 127.0.0.1 before they resolve to the correct IP.

Impact: Java applications try to connect to localhost and fail. In this case the Java app is Intel TXT, so this is customer impacting.

Manual fix: Remove all 127.0.0.1 entries for fuel server and restart dnsmasq.

[Andrew Woodward (xarses)]

I spoke with Christian, this is a 3.2.0 deployment. The root cause here is that we are adding 127.0.0.1 <hostname> into /etc/hosts, when it should be <current ip> <hostname>. The multiple instances of this in /etc/hosts on the fuel node is likely due to bootstrap_admin_node being run multiple times

[Vladimir Kuklin (vkuklin)]

Matt, could you comment if this bus was resolved in 3.2.1 or not?

[Matthew Mosesohn (raytrac3r)]

Vladimir, Andrew, this was fixed for 3.2.1 and 4.0 already in this bug:
https://bugs.launchpad.net/fuel/+bug/1247069

The extra entry was made before in Fuel 3.2 when a user disabled all network interfaces in Fuel Menu. There were some Puppet issues with trying to apply l23network changes with no valid IP address, so it's no longer possible to configure the system with no IP address and this scenario should not repeat in 3.2.1 or 4.0.

[Christian Huebner (ossarchitect)]

In my case the network interfaces were normal and when resolving the
host name it would come up with 7 or 8 entries for 127.0.0.1 and one
(the last one in the list) with the correct address 10.20.0.2

As I did not disable all network interfaces this may be a different bug
and should be investigated.

Thanks

Christian

On 12/12/13, 9:07 AM, Matthew Mosesohn wrote:
> Vladimir, Andrew, this was fixed for 3.2.1 and 4.0 already in this bug:
> https://bugs.launchpad.net/fuel/+bug/1247069
>
> The extra entry was made before in Fuel 3.2 when a user disabled all
> network interfaces in Fuel Menu. There were some Puppet issues with
> trying to apply l23network changes with no valid IP address, so it's no
> longer possible to configure the system with no IP address and this
> scenario should not repeat in 3.2.1 or 4.0.

[Andrew Woodward (xarses)]

Assigning to me to verify if this is still a problem; retargeted to 4.1

[Andrew Woodward (xarses)]

confirmed, should be fixed in 4.0

[root@nailgun ~]# cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
10.108.10.2 nailgun.test.domain.local