Comment 0 for bug 1432821

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

I'm seeing 2 different issues here.
a.) something is specifcally deleting /run/network/
   I say specifically, because if I change '/run/network' above to '/run/xnetwork', including the symlink, then it works as designed.

b.) resolvconf seems not to be working as well as it should be.
   in all other supported ubuntu releases, doing the abovel results in functional resolv.conf via resolv.conf.

I'm not sure what is doing the cleaning, but it is after the pivot root, and before I log in to look.