yahoo-eng-team team mailing list archive

[Chad Smith <1956788@xxxxxxxxxxxxxxxxxx>]

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


** Changed in: cloud-init
       Status: Fix Released => New

** Changed in: cloud-init
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1956788

Title:
  system_cfg not read on Oracle datasource

Status in cloud-init:
  In Progress

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1956788/+subscriptions