yahoo-eng-team team mailing list archive

[Dimitri John Ledkov <launchpad@xxxxxxxxxxxx>]

casper has been changed to generate cloud.cfg instead of netplan, thus
no further work in cloud-init is required for focal.

Closing this issue as fix released in casper & z project.

It would be nice for cloud-init to do what was originally asked, but
that is a feature request of a lower priority now, that needs further
spec / implementation as discussed on github PR.

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

** Changed in: ubuntu-z-systems
       Status: In Progress => Fix Released

** Changed in: casper (Ubuntu)
       Status: New => 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/1861460

Title:
  cloud-init should parse initramfs rendered netplan if present

Status in cloud-init:
  Invalid
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in casper package in Ubuntu:
  Fix Released

Bug description:
  initramfs-tools used to only execute klibc based networking with some
  resolvconf hooks.

  In recent releases, it has been greatly improved to use
  isc-dhcp-client instead of klibc, support vlan= key (like in
  dracut-network), bring up Z devices using chzdev, and generate netplan
  yaml from all of the above.

  Above improvements were driven in part by Oracle Cloud and in part by
  Subiquity netbooting on Z.

  Thus these days, instead of trying to reparse klibc files in
  /run/net-*, cloud-init should simply import /run/netplan/$device.yaml
  files as the ip=* provided networking information on the command line.
  I do not currently see cloud-init doing that in e.g.
  /cloudinit/net/cmdline.py

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