yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1956788@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package cloud-init - 23.2.1-0ubuntu0~22.10.1

---------------
cloud-init (23.2.1-0ubuntu0~22.10.1) kinetic; urgency=medium

  * Upstream snapshot based on 23.2.1. (LP: #2025180).
    List of changes from upstream can be found at
    https://raw.githubusercontent.com/canonical/cloud-init/23.2.1/ChangeLog

cloud-init (23.2-0ubuntu0~22.10.1) kinetic; urgency=medium

  * d/control: Remove pep8 dependency. It is no longer used.
  * d/apport-general-hook.py: Add general apport hook to append cloud type,
    image and instance size information to bug reports (LP: #1724623)
  * d/cloud-init.preinst: Oracle to remove vestigial /etc/cloud.cloud.cfg.d/
    99-disable-network-config.cfg because system config is now honored before
    datasource config (LP: #1956788)
  * d/cloud-init.preinst: Clean up vestigial
    /etc/cloud/cloud.cfg.d/99-disable-network-activation.cfg on GCE instances
    after fix in upstream google-guest-agent.
  * Upstream snapshot based on 23.2. (LP: #2023110).
    List of changes from upstream can be found at
    https://raw.githubusercontent.com/canonical/cloud-init/23.2/ChangeLog

 -- Brett Holman <brett.holman@xxxxxxxxxxxxx>  Wed, 28 Jun 2023 14:24:21
-0600

** Changed in: cloud-init (Ubuntu Kinetic)
       Status: Fix Committed => Fix Released

-- 
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:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Focal:
  Fix Released
Status in cloud-init source package in Jammy:
  Fix Released
Status in cloud-init source package in Kinetic:
  Fix Released

Bug description:
  [ Impact ]

  Prefer system_cfg for network configuration on Oracle above the
  dataousrce config to allow images to dictate network overrides in
  /etc/cloud/cloud.cfg.d when necessary. Without this configuration,
  certain image launches on Orale will not be able to receive correct
  network at VM launch time resulting in inaccessible VMs via SSH.

  [ Test Plan ]

  Procedure for validation (will be scripted as best we can)

  1. Launch Oracle vm for focal, jammy, kinetic and lunar
  2. Confirm presence of /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg 
  3. Upgrade cloud-init to -proposed
  4. confirm absence of /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
  5. Reboot this VM to test default launch without 99-disable-network-config succeds on fresh launches
  6. sudo cloud-init clean --logs; sudo shutdown -h now
  6. Export VM to Oracle Object Storage
  7. Launch from exported object storage image to trigger reading network config from IMDS instead of ISCSI
  8. Assert ssh to instance works and no Tracebacks in /var/log/cloud-init.log

  [ Where problems could occur ]
  If this patch is unsuccessful, default new instance launches on Oracle or launches from Object storage would timeout and disallow SSH because cloud-init didn't set up network appropriately.

  [ Other Info ]

  [Original 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