[Bug 1432758] [NEW] cloud-config.service, cloud-final.service do not run if previous cloud-init service failed

[Scott Moser]

Public bug reported:

cloud-init has 4 basic jobs:
 cloud-init-local: local search for datasource
 cloud-init: network search for datasource,
 cloud-config: some modules, runs right after datasource found
 cloud-final : rc.local timeframe

each expects the previous to have finished, but does not need it or
expect it to have exited successfully.

in upstart, failure of one job does not stop the running of another.
However, in systemd failure (exit non-zero) of any job seems to result in subsequent jobs not running.

For instance, a system i just booted had a failure of one of the config
modules that runs in cloud-init stage.  so cloud-init exited non-zero.
That resulted in:

[FAILED] Failed to start Initial cloud-init job (metadata service crawler).
See "systemctl status cloud-init.service" for details.
[DEPEND] Dependency failed for Cloud-config availability.
[DEPEND] Dependency failed for Apply the settings specified in cloud-config.
[DEPEND] Dependency failed for Execute cloud user/final scripts.

** Affects: cloud-init (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1432758

Title:
  cloud-config.service, cloud-final.service do not run if previous
  cloud-init service failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1432758/+subscriptions