Local BOA install sets nameserver to itself and fails to resolve it's own hostname to an ip

[karudonaldson]

How to prevent resolveconf from setting localhost/127.0.0.1 as the primary resolver, or perhaps the question is how to set an external dns nameserver as primary resolver so it won't be overridden at install time?

[karudonaldson]

I added to /etc/network/interfaces
dns-search example.com
dns-nameservers 192.168.3.45 192.168.8.10

[karudonaldson]

For some reason the local install is reverting the /etc/resolv.conf to use itself as dns. Is there a way I can use an alternative dns nameserver rather than itself? For the life of me I can't figure out why it keeps reverting?

[karudonaldson]

Once barracuda finishes and octopus install starts the result is:
Octopus [Thu Aug 7 10:40:11 NZST 2014] ==> INIT A: FATAL ERROR: This server does not have a hostname that resolves to an IP address
Octopus [Thu Aug 7 10:40:11 NZST 2014] ==> INIT A: FATAL ERROR: Aborting AegirSetupA installer NOW!
Octopus [Thu Aug 7 10:40:11 NZST 2014] ==> FATAL ERROR: AegirSetupA installer failed
Octopus [Thu Aug 7 10:40:11 NZST 2014] ==> FATAL ERROR: Aborting Octopus installer NOW!

Is this hard coded somewhere?

[omega8cc]

We don't actively support nor test the localhost mode, as clearly mentioned in the README: https://github.com/omega8cc/boa/blob/master/README.txt#L87

We may work on this again in the future, but currently it has very low (none) priority, so please submit any fixes you can, but don't expect debugging on our side at the moment.

[karudonaldson]

It does appear to have no benefit running "local". It seems a "public" build works just fine for local installs.

[Amstercad]

Here's how I tried to install BOA on a LAN/VM with limited success today, and what was returned to me when using Debian 7.6.0. (Notice I use the combo of 'in-stable public', just so the installer would run, which was progress from earlier failures)

root@aegir:~# boa in-stable public localhost exampleuser@example.com all

[...extraneous text deleted -Amstercad]

Barracuda [Sun Sep 14 10:15:54 CEST 2014] ==> INFO: Checking your system version...
/var/backups/BARRACUDA.sh.txt: line 5680: lsb_release: command not found
/var/backups/BARRACUDA.sh.txt: line 5681: lsb_release: command not found
Barracuda [Sun Sep 14 10:15:54 CEST 2014] ==> == FATAL ERROR ==
Barracuda [Sun Sep 14 10:15:54 CEST 2014] ==> Invalid install script or OS used
Barracuda [Sun Sep 14 10:15:54 CEST 2014] ==> It is not any supported Debian or Ubuntu version
Barracuda [Sun Sep 14 10:15:54 CEST 2014] ==> You need Debian - Squeeze (recommended) or Wheezy
Barracuda [Sun Sep 14 10:15:54 CEST 2014] ==> or Ubuntu - Precise or Lucid
Octopus [Sun Sep 14 10:15:54 CEST 2014] ==> ALRT: Percona server not running properly!
Octopus [Sun Sep 14 10:15:54 CEST 2014] ==> EXIT: We can't proceed and will exit now
Octopus [Sun Sep 14 10:15:54 CEST 2014] ==> HINT: Please (re)start Percona server and then run installer again
Octopus [Sun Sep 14 10:15:54 CEST 2014] ==> Bye

BOA in-stable completed
Bye

[Amstercad]

I think this bug has been fixed. Today I went to the same virtual machine as before, using a snapshot, so the only thing different was newer BOA scripts. And the local (aegir.local) install was successful today. I didn't have time to do really extensive testing, but I can at least report this now.

I will be doing more extensive testing in the coming weeks, because I really like installing BOA everywhere, including the LAN. (I use drush rsync and drush sql-sync to push up dev-sites to the public server, and need to find/read docs, on how to use these cool BOA features!)

[karudonaldson]

I can confirm that after much testing the installer still forces an update of /etc/resolv.conf to contain
nameserver 127.0.0.1
This seems to take precedence over my configured nameserver entry in /etc/network/interfaces and in the dynamic resolvconf file "/etc/resolvconf/resolv.conf.d/base"

This ends up breaking both barracuda and octopus install or upgrade.

Work around solution is to open /etc/resolv.conf file in one session add the entry for a local network nameserver for example:
nameserver 192.168.1.1
then, open a 2nd session to run an install/upgrade.
Important: Immediately after you start the install or upgrade, switch back to the first session and force overwrite the /etc/resolv.conf file with your nameserver entry and the install process will complete.

If there was an way to override the nameserver entry to only use a configured IP then this issue wouldn't be occurring I believe.

Hope that is of some use.

[Amstercad]

If it helps for me to be more clear, in my testing, I was only trying to get a new fresh installation to work as localhost.