system_cfg not read on Oracle datasource

[James Falcon]

In https://github.com/canonical/cloud-init/commit/2c52e6e88b19f5db8d55eb7280ee27703e05d75f , the order of reading network config was changed for Oracle due to initramfs needing to take lower precedence than the datasource. However, this also bumped system_cfg to a lower precedence than ds, which means that any network configuration specified in /etc/cloud will not be applied.

system_cfg should instead be moved above ds so network configuration in /etc/cloud takes precedence.

[Brett Holman (holmanb)]

This bug is believed to be fixed in cloud-init in version 22.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

[Chad Smith (chad.smith)]

This fix in Jammy 22.1-14-g2e17a0d6-0ubuntu1~22.04.1 also had an unintended side-effect where network would not get rendered due and newly launched instnaces on Jammy were unreachable due to
cloud-init networking being configured as disabled in Oracle images /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg.

This commit is being reverted for this release so it can be refactored to avoid the side-effect.
https://github.com/canonical/cloud-init/pull/1326

[James Falcon (falcojr)]

Every Oracle instance boots with /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg as it was probably intended to ensure only iSCSI configuration is used. While this seems unnecessary to me, there are currently no plans to change this, so I see no reason to keep this bug open.

[Fabio Augusto Miranda Martins (fabio.martins)]

CPC has worked on removing /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg from Oracle images and this is completed started with Images with build >=20221123

I just used our daily images to create 3 custom images with:

- Jammy: 20221214
- Focal: 20221214
- Bionic: 20221205

And launched J/F/B bare-metal instances and I can validate this doesn't cause any issues and the networking is working well on all 3 releases:

https://pastebin.ubuntu.com/p/nX7dM7mQSQ/

I believe next step is to proceed with the change proposed by this LP.

As a reminder, as part of a post-install script, we'll need to remove /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg if it exists, so that we don't break network for existing instances when they upgrade cloud-init.

Marking back as ~~triaged~~ confirmed, since we removed /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg fropm the images, which prevented our work here.

EDIT: Marking as confirmed, as I can't mark as Triaged

[Alberto Contreras (aciba)]

Being fixed in:

https://github.com/canonical/cloud-init/pull/1998
https://github.com/canonical/cloud-init/pull/2014

[Chad Smith (chad.smith)]

Upstream commit landed for this feature https://github.com/canonical/cloud-init/commit/6b9bf7b9bb2db20b7d254f0143df343e14f4c7d4

expected release cloud-init version 23.2. It'll publish sooner into 23.04 (Lunar) in a 23.1.1-## interim snapshot.

[Chad Smith (chad.smith)]

Related changeset in Lunar packaging to remove config artifacts across upgrade path on Oracle: https://github.com/canonical/cloud-init/pull/2046

[Fabio Augusto Miranda Martins (fabio.martins)]

I see per the comments that this is being released to Lunar. Is there a plan to backport it to B / F / J?

[James Falcon (falcojr)]

Fabio, this one missed the 23.1 release, which is currently in the process of being SRUed. It will make if to F, J, and K (not B as it will be EOL) once 23.2 lands in about 3 months.

[Alberto Contreras (aciba)]

F, J, K PRs:

https://github.com/canonical/cloud-init/pull/2068
https://github.com/canonical/cloud-init/pull/2069
https://github.com/canonical/cloud-init/pull/2070