Merge lp:~nobuto/maas-deployer/fix-resolvconf into lp:~maas-deployers/maas-deployer/next

[Nobuto Murata]

properly clean up /etc/resolv.conf, LP: #1480263

/etc/resolv.conf will be left as empty until the next reboot, but it
uses local nameserver, i.e. MAAS DNS. From the manpage of
resolv.conf(5):
> If no nameserver entries are present, the default is to use the name
> server on the local machine.

=== modified file 'maas_deployer/vmaas/templates/config-maas.sh'
--- maas_deployer/vmaas/templates/config-maas.sh	2015-07-23 16:20:28 +0000
+++ maas_deployer/vmaas/templates/config-maas.sh	2015-08-19 14:05:30 +0000
@@ -14,11 +14,10 @@
 # Configure the dns nameservers
 echo "Configuring the DNS nameserver"
 for dev in `ip link show | grep eth.*mtu | cut -d':' -f2`; do
-  sudo resolvconf -d $dev
+  sudo resolvconf -d ${dev}.inet
 done
 
 sudo sed -i 's/dns-nameserver.*/dns-nameserver 127.0.0.1/g' /etc/network/interfaces
-sudo resolvconf -u
 
 
 # Generate a MAAS API key for the admin user and start the importing of boot resources.