Le Mon, Sep 07, 2015 at 06:04:06PM +0200, Michael Biebl a écrit : > > The bug reporter claims that cloud-init-local needs to run during early > boot (rcS) before networking (typically /etc/init.d/networking) has started. > If this is true, and cloud-init-local really needs to start that early, > the cloud-init-local SysV init script is broken and the fix in > 0.7.6~bzr976-3 is incomplete, as it only applies to systemd. Fixing the > LSB header should also make it work correctly under systemd without the > need to add new .service files in a stable upload.
> Given the above, I'm re-opening the bug report, since the fix is > incomplete and/or the justification why it's ok to run > "/usr/bin/cloud-init --local" early during boot under systemd but not > under sysvinit. Hi Michael, thank you for your analysis. On my side, I will not be able to produce a correction for sysvinit by myself. Other uploaders may comment on that issue... Regarding the systemd unit files, do you think that it is too risky to enable them by a point release ? Systemd is the default init system after all, and the unit files enabled here are almost identical to the upstream ones. Alternatively, we can keep cloud-init broken in Jessie, or request its removal if the breakage is too large. Have a nice day, -- Charles Plessy Tsurumi, Kanagawa, Japan
