[Touch-packages] [Bug 1869155] Re: When installing with subiquity, the generated network config uses the macaddress keyword on s390x (where MAC addresses are not necessarily stable across reboots)

Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3634 ** Bug watch added: github.com/canonical/cloud-init/issues #3634 https://github.com/canonical/cloud-init/issues/3634 -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1869155] Re: When installing with subiquity, the generated network config uses the macaddress keyword on s390x (where MAC addresses are not necessarily stable across reboots)

** Changed in: subiquity Status: New => Fix Released ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-z-systems Status: New => Fix Released ** Changed in: cloud-init Status: Incomplete => Invalid -- You received this bug

[Touch-packages] [Bug 1869155] Re: When installing with subiquity, the generated network config uses the macaddress keyword on s390x (where MAC addresses are not necessarily stable across reboots)

I retried with a fresh installation. Prior to the 'Network connection' subiquity step/screen there is no network yaml config in /etc/cloud/cloud.cfg.d/, but in /etc/netplan: root@ubuntu-server:/# ls -l /etc/cloud/cloud.cfg.d/ total 4 -rw-r--r-- 1 root root 2057 Mar 10 14:22 05_logging.cfg

[Touch-packages] [Bug 1869155] Re: When installing with subiquity, the generated network config uses the macaddress keyword on s390x (where MAC addresses are not necessarily stable across reboots)

Pretty sure it's initramfs-tools that is putting the mac addresses in the netplan. That probably needs to grow a little platform-dependent behaviour around this. ** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because