dyn-netconf IP re-writing runs too early (before load_modules)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-initramfs-tools (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
currently the dyn-netconf script that re-writes IP= and BOOTHOOK= runs at init-top.
per initramfs-tools(8)
| init-top the scripts in this directory are the first scripts to
| be executed after sysfs and procfs have been mounted. It also
| runs the udev hook for populating the /dev tree (udev will keep
| running until init-bottom).
since we were not declaring a dependency on udev, udev might not even
be running at that point, so the 'udev_wait' that we do there will
probably be useless.
The fix here I think is to just run at 'init-premount':
| init-premount happens after modules specified by hooks and
| /etc/initramfs-
This seems like a sane place to run, and then we'll make sure that
the specific modules are loaded also (ie, 'load_modules' will have run).
Changed in cloud-initramfs-tools (Ubuntu): | |
status: | New → In Progress |
importance: | Undecided → Medium |
This bug was fixed in the package cloud-initramfs -tools - 0.19ubuntu1
--------------- -tools (0.19ubuntu1) raring; urgency=low
cloud-initramfs
* cloud-initramfs -growroot: support growpart exit status of '1' necessary" -dyn-netconf: run at init-premount rather than
indicating "no-change-
* cloud-initramfs
init-top to ensure that 'load_modules' has been run and udev is
running (LP: #1116426)
-- Scott Moser <email address hidden> Tue, 05 Feb 2013 16:49:23 -0500