networking comes up parallel to cloud-init-local

Bug #1368861 reported by Scott Moser
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Expired
Undecided
Unassigned

Bug Description

This is a similar bug to bug 1225922.
but this is more just the first part.
The user can provide networking information to cloud-init via a local datasource.
However, if there is networking information already, those devices might already be up.

The suggested fix here is to block networking from coming up until after cloud-init-local is up.

This way, a local datasource can reliably insert definitive networking and not have to fight with information already present (such as default 'eth0' network info).

Related branches

Revision history for this message
Will Bryant (willbryant) wrote :

Apologies for a stupid question but on Xenial, cloud-init-local.service has Before=network-pre.target, so would that have fixed this?

I'm a bit confused about what happens during init local - I am testing out NoCloud using uvt-kvm, and apart from the "Cloud-init v. 0.7.8 running 'init-local'" banner, I don't see any output from the first cloud-init process.

The expected output doesn't seem to happen until the second service starts, "Starting Initial cloud-init job (metadata service crawler)", which is after the "Started Raise network interfaces." and "Reached target Network.".

So I feel like I am misunderstanding what init local does?

Revision history for this message
Will Bryant (willbryant) wrote :

Ah, you need dsmode: local in the meta-data file.

So yeah, this looks fixed when using systemd?

Revision history for this message
Joshua Powers (powersj) wrote :

Hi Will!

Thank you for taking the time to report this bug. In an effort to keep
an up-to-date and valid list of bugs to work on, I have reviewed this
report verifying it still requires effort and occurs on a supported
version of Ubuntu.

Take a read first at the boot stage document:
https://cloudinit.readthedocs.io/en/latest/topics/boot.html

The local stage blocks networking from coming up in the first place as
you suggested in your bug report. This allows local datasources to
provide input on the system configuration. Then the service stage
brings up networking.

My apologies that you did not receive a more prompt reply. I am however
moving the bug to 'Incomplete'. If you disagree or have new information,
we would be grateful if you could please add a comment stating why and
then change the status of the bug to 'New'.

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 :
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.