yahoo-eng-team team mailing list archive

[Steve Langasek <1956788@xxxxxxxxxxxxxxxxxx>]

Hello James, or anyone else affected,

Accepted cloud-init into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/23.2-0ubuntu0~22.10.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags added: verification-needed verification-needed-kinetic

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Kinetic)
   Importance: Undecided
       Status: New

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

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

** Changed in: cloud-init (Ubuntu Jammy)
       Status: New => Fix Committed

** Tags added: verification-needed-jammy

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

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