cloud-init-local would fail on NFS if no networking

[Joonas Kylmälä]

The cloud-init-local systemd service's executable is stored in /usr/bin. Also the service is currently run before networking has started. If a person wants to use NFS for /usr then it would mean that cloud-init-local service could not be run. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805866#40 for further information.

I also think that it is weird that the Debian's sysvinit file has $remote_fs as start requirement (it's the opposite of systemd service file):
# Required-Start: $local_fs $remote_fs

However the redhat sysvinit file doesn't have $remote_fs as requirement for start which makes this even more confusing.

Files related to this bug:
    cloud-init/sysvinit/redhat/cloud-init-local
    cloud-init/sysvinit/debian/cloud-init-local
    cloud-init/systemd/cloud-init-local.service

[Dan Watkins (oddbloke)]

Hi Joonas,

Thanks for filing this bug! It looks to me like this is fixed in more recent releases of cloud-init. If you disagree, please do set this bug back to New (with explanation, of course!).

Thanks!

Dan

[James Falcon (falcojr)]

Tracked in Github Issues as https://github.com/canonical/cloud-init/issues/2933