/etc/resolv.conf is not updated

[Nobuto Murata]

After the deployment, /etc/network/interfaces has "dns-nameserver 127.0.0.1". However /etc/resolv.conf(/run/resolvconf/resolv.conf) still has old entries, i.e. name resolution of MAAS nodes does not work.

[vmaas/templates/config-maas.sh]
...
     14 # Configure the dns nameservers
     15 echo "Configuring the DNS nameserver"
     16 for dev in `ip link show | grep eth.*mtu | cut -d':' -f2`; do
     17 sudo resolvconf -d $dev
     18 done
     19
     20 sudo sed -i 's/dns-nameserver.*/dns-nameserver 127.0.0.1/g' /etc/network/interfaces
     21 sudo resolvconf -u
...

I belivieve the pair of "resolvconf -d eth0.inet && resolvconf -a eth0.inet" is needed to update /etc/resolv.conf properly.

[Nobuto Murata (nobuto)]

A quick workaround is `sudo ifdown eth0 && sudo ifup eth0` or just reboot.

[Edward Hope-Morley (hopem)]

This change is breaking deployments. Specifically it prevents MAAS from being able to download images since it is unable to resolve maas.ubuntu.com once the original nameserver is removed.

There is also possibly a bug with how we are using the local datasource with cloud-init to configure networking since on reboot /e/n/i is always overwritten with the contents of the metadata section in the local datasource. We will also need a more intelligent way to work out what nameservers are configured and on what interface(s) and apply then accordingly with e.g.

echo "nameserver 127.0.0.1"| sudo resolvconf -a eth0.inet

So, i'm going to revert this for now until we find a better solution.

[Edward Hope-Morley (hopem)]

After some discussion with wolsen i think we can get this fixed up for 0.0.2. Will submit an additional patch shortly.