[Bug 1047712] Re: container-detect.conf should be 'start on virtual-filesystems'
smoser at ubuntu.com
Sat Sep 8 02:42:55 UTC 2012
now that i think about it there is a race if we back resolvconf.conf to start on virtual-filesystems.
in that as soon as that event occurs networking could come up before resolvconf has had a chance to prep itself.
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
container-detect.conf should be 'start on virtual-filesystems'
Status in “resolvconf” package in Ubuntu:
Status in “upstart” package in Ubuntu:
I'm running into some issues during my "ephemeral boot" (iscsi read-only root) work for maas.
In debugging bug 1031065, we had 'cloud-init-nonet' actually mount all virtual-filesystems and then emit the event.
After doing that, we were still timing out on networking coming up
because of a dependency on specifically 'mounted mountpoint=/run' by
changing that to 'start on virtual-filesystems' improves my situation.
DistroRelease: Ubuntu 12.10
Package: upstart 1.5-0ubuntu8
ProcVersionSignature: User Name 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
Date: Sat Sep 8 02:10:46 2012
PATH=(custom, no user)
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
More information about the foundations-bugs