The fix that went in to xenial for this (and present in current yakkety
and trunk cloud-init) is for cloud-init to read its networking
configuration effectively from the kernel command line.
If cloud-init sees network-config= or ip= on the kernel command line,
then it will parse the /run/net-*.conf files that are written by the
ipconfig in the initramfs and use them as a source of networking
information. The kernel's command line overrides a datasource or
builtin configuration, so the end result is that the 'ip=' declares the
system's network configuration.
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu)
Status: New => Fix Released
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
** No longer affects: cloud-initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534205
Title:
cloud-initramfs-dyn-netconf should work without
/etc/network/interfaces symlink
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1534205/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
