cloud-init

Network.service not always finishing before cloud-init.service starts on centOS

Bug #1713104 reported by Scott Easum
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Expired
Undecided
Unassigned

Bug Description

While https://github.com/cloud-init/cloud-init/commit/dcbe479575fac9f293c5c4089f4bcb46ab887206#diff-27b6e651d75e0328135ddc43d3a83703 helped standardize systemd across distros, we have run into intermittent network failures for CentOS after using it.

~5% of provisions fail with "Job network.service/start deleted to break ordering cycle starting with cloud-init.service/start"

A re-run of cloud-init will fix this problem as a workaround.

Revision history for this message
Robie Basak (racb) wrote :

Thank you for the report. Since the report is about CentOS rather than Ubuntu I'm changing the bug task from cloud-init in Ubuntu to cloud-init upstream.

affects: cloud-init (Ubuntu) → cloud-init
Revision history for this message
Scott Moser (smoser) wrote :

Scott,

Can you please run 'cloud-init collect-logs' on a system that has failed and post the result here?
Then also set the 'Status' back to New.

Thanks.

Changed in cloud-init:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cloud-init because there has been no activity for 60 days.]

Changed in cloud-init:
status: Incomplete → Expired
Revision history for this message
James Falcon (falcojr) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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