maas images utilize cloud-initramfs-dyn-netconf . The way this works is basically:
* /etc/network/interfaces in image is a link to ../../run/network/dynamic-interfaces
* kernel command line 'ip=' convince the initramfs to bring up networking using 'ipconfig'
example: ip=::::maas-enlist:BOOTIF
* ipconfig writes files in /run/net-*.conf for each interface it configures.
* cloud-initramfs-dyn-netconf module writes /run/network/dyanmic-interfaces based on /run/net-*.conf files that 'ipconfig' creates.
end result is that after the move to real root, /etc/network/interfaces should be a symlink to /run/ that ends up having something like this:
| ## This file is generated by cloud-initramfs-dyn-netconf
| auto lo
| iface lo inet loopback
| manual eth0
| iface eth0 inet dhcp
| dns-nameservers 192.168.64.3
| dns-search maas
resolvconf seems not to be working as well as it should be. In vivid (now using systemd), I have only the resolvconf header in the file.
in all other supported ubuntu releases, doing the above results in functional resolv.conf via resolv.conf. Seen here from trusty:
| # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
| # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
| nameserver 192.168.64.3
Related Bugs:
* bug 1432821: something deleting /run/network after during boot
* bug 1463461: resolvconf not updated by /lib/systemd/system/ifup@.service.d/open-iscsi.conf
* bug 1501033: transient error results in /etc/resolv.conf not populated in iscsi root
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: resolvconf 1.69ubuntu1.1
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
Date: Mon Mar 16 20:42:24 2015
PackageArchitecture: all
ProcEnviron:
TERM=vt102
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: resolvconf
UpgradeStatus: No upgrade log present (probably fresh install)
First a parenthetical remark. According to interfaces(5) the "manual" keyword is used exclusively in the "method" field, as in `iface eth0 inet manual`. But in your example you use it at the beginning of a line. Perhaps you think that in that context "manual" means the opposite of "auto" (non-auto?) but so far as I can tell by reading the manual page and the source code it does not have any meaning in that context. If a logical interface is not declared as "auto" then it is non-auto and there is no way affirmatively to declare a logical interface as non-auto. If I am right, please see to it that the software you are using gets fixed so that it doesn't write out meaningless "manual ..." lines. If I am not right then please let me know. :)
The submitter wrote:
| ## This file is generated by cloud-initramfs
| auto lo
| iface lo inet loopback
| manual eth0
| iface eth0 inet dhcp
| dns-nameservers 192.168.64.3
| dns-search maas