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

Bug #1432758 reported by Scott Moser
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Fix Released
High
Unassigned

Bug Description

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.

Related branches

Scott Moser (smoser)
Changed in cloud-init (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-init - 0.7.7~bzr1084-0ubuntu1

---------------
cloud-init (0.7.7~bzr1084-0ubuntu1) vivid; urgency=medium

  * New upstream snapshot.
    * systemd: update config and final to run even if init jobs fail
      (LP: #1432758)
    * emit_upstart: fix use of undeclared variable
    * SmartOS: fixes for python3 reading from serial device.
 -- Scott Moser <email address hidden> Tue, 17 Mar 2015 16:48:42 -0400

Changed in cloud-init (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.