networking comes up parallel to cloud-init-local

[ubuntu-server-builder]

This bug was originally filed in Launchpad as LP: #1368861

Launchpad details

affected_projects = []
assignee = None
assignee_name = None
date_closed = 2018-01-26T04:17:35.101050+00:00
date_created = 2014-09-12T16:46:02.375880+00:00
date_fix_committed = None
date_fix_released = None
id = 1368861
importance = undecided
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1368861
milestone = None
owner = smoser
owner_name = Scott Moser
private = False
status = expired
submitter = smoser
submitter_name = Scott Moser
tags = []
duplicates = []

Launchpad user Scott Moser(smoser) wrote on 2014-09-12T16:46:02.375880+00:00

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

[ubuntu-server-builder]

Launchpad user Will Bryant(willbryant) wrote on 2016-11-08T09:33:35.384479+00:00

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?

[ubuntu-server-builder]

Launchpad user Will Bryant(willbryant) wrote on 2016-11-08T10:58:25.721166+00:00

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

So yeah, this looks fixed when using systemd?

[ubuntu-server-builder]

Launchpad user Joshua Powers(powersj) wrote on 2017-07-27T21:27:59.990736+00:00

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

[ubuntu-server-builder]

Launchpad user Launchpad Janitor(janitor) wrote on 2018-01-26T04:17:34.977237+00:00

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