Control: found -1 0.7.6~bzr976-3 I looked at the cloud-init package in testing/unstable. The LSB header of /etc/init.d/cloud-init-local has
### BEGIN INIT INFO # Provides: cloud-init-local # Required-Start: $local_fs $remote_fs # Required-Stop: # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Cloud init local # Description: Cloud configuration initialization ### END INIT INFO 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. That said, I don't know, if /usr/bin/cloud-init can actually run that early during boot. Since the binary is in /usr, this is not going to work if one want's to support the mythical /usr-on-NFS. This is something where we need input from the maintainer. 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. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
