Setting net.ifnames=0 in livecd-rootfs was a quick hack for wily, but
this is really inconvenient. This means that the cloud images now stop
being usable for non-cloud workloads (or even for cloud workloads with
multiple NICs).
The proper fix would be for cloud-init to generate a network config on
first boot, for the first /sys/class/e* interface, instead of shipping a
hardcoded /etc/network/interfaces.d/eth0.cfg. Can we please do this for
xenial?
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: cloud-init (Ubuntu Wily)
** Changed in: cloud-init (Ubuntu Xenial)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510345
Title:
[SRU] Cloud Images do not bring up networking w/ certain virtual NICs
due to device naming rules
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-on-ec2/+bug/1510345/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
