Some conversation in ubuntu-devel yesterday [1]. This seems to have been caused by the fix for bug 800824. That change [2] was done to address failure of networking to appear as started a container. Per Steve, "that looks like a wrong workaround for bug #925122".
Hopefully what that means is we can remove this code and lxc containers still boot correctly even in precise (in which case we should probably SRU that). -- [1] http://irclogs.ubuntu.com/2012/07/31/%23ubuntu-devel.html#t01:41 [2] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/405 ** Summary changed: - /sbin/resolvconf -a depends on /run/resolvconf/interface but it may not exist + cloud-init-nonet runs 'start networking' explicitly ** Description changed: In development of 'overlayroot' package, I was mounting / as rw in the initramfs. This was causing a different order of execution of mounts, and as a result a different order of networking resolvconf and networking bringup. It exposed a bug in resolvconf, which was being called on boot in this order: ==== Mon Jul 30 19:08:58 UTC 2012 /sbin/resolvconf -a lo.inet ==== ==== Mon Jul 30 19:08:59 UTC 2012 /sbin/dhclient-script ==== ==== Mon Jul 30 19:08:59 UTC 2012 /sbin/resolvconf -a eth0.dhclient ==== ==== Mon Jul 30 19:08:59 UTC 2012 /sbin/resolvconf -a eth0.inet ==== ==== Mon Jul 30 19:08:59 UTC 2012 /sbin/resolvconf --enable-updates ==== ==== Mon Jul 30 19:08:59 UTC 2012 /etc/resolvconf/update.d/libc -u ==== The normal order is for resolvconf --enable-updates to be called (from /etc/init/resolvconf.conf) before anything else. As a result, I was seeing errors like: - resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory + resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory This may be exposing a more grave issue, in that I believe the reason for dhclient coming up before resolvconf.conf started was that it was being run as a result of /etc/init/network-interface.conf. I don't immediately see how that is guarnateed to have /run ounted at all. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: resolvconf 1.67ubuntu1 ProcVersionSignature: User Name 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic x86_64 Architecture: amd64 Date: Mon Jul 30 20:07:04 2012 PackageArchitecture: all ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) + + Related Bugs: + * bug 800824: cloud-init-nonet times out in lxc Edit + * bug 925122: container's udevadm trigger --add affects the host ** Description changed: In development of 'overlayroot' package, I was mounting / as rw in the initramfs. This was causing a different order of execution of mounts, and as a result a different order of networking resolvconf and networking bringup. It exposed a bug in resolvconf, which was being called on boot in this order: ==== Mon Jul 30 19:08:58 UTC 2012 /sbin/resolvconf -a lo.inet ==== ==== Mon Jul 30 19:08:59 UTC 2012 /sbin/dhclient-script ==== ==== Mon Jul 30 19:08:59 UTC 2012 /sbin/resolvconf -a eth0.dhclient ==== ==== Mon Jul 30 19:08:59 UTC 2012 /sbin/resolvconf -a eth0.inet ==== ==== Mon Jul 30 19:08:59 UTC 2012 /sbin/resolvconf --enable-updates ==== ==== Mon Jul 30 19:08:59 UTC 2012 /etc/resolvconf/update.d/libc -u ==== The normal order is for resolvconf --enable-updates to be called (from /etc/init/resolvconf.conf) before anything else. As a result, I was seeing errors like: resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory This may be exposing a more grave issue, in that I believe the reason for dhclient coming up before resolvconf.conf started was that it was being run as a result of /etc/init/network-interface.conf. I don't immediately see how that is guarnateed to have /run ounted at all. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: resolvconf 1.67ubuntu1 ProcVersionSignature: User Name 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic x86_64 Architecture: amd64 Date: Mon Jul 30 20:07:04 2012 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) Related Bugs: - * bug 800824: cloud-init-nonet times out in lxc Edit - * bug 925122: container's udevadm trigger --add affects the host + * bug 800824: cloud-init-nonet times out in lxc + * bug 925122: container's udevadm trigger --add affects the host -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1031065 Title: cloud-init-nonet runs 'start networking' explicitly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1031065/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs