** Changed in: cloud-init (Debian) Status: Incomplete => Fix Released
-- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1700338 Title: cloud-init-local would fail on NFS if no networking Status in cloud-init: New Status in cloud-init package in Debian: Fix Released Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1700338/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp