yahoo-eng-team team mailing list archive

[Fabio Augusto Miranda Martins <1956788@xxxxxxxxxxxxxxxxxx>]

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

** Changed in: cloud-init
       Status: Invalid => Confirmed

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

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