Public bug reported:
Binary package hint: cloud-init
Persistent interface naming should be disabled in UEC images, as it
causes more harm that good.
Firstly, cloud systems generally expect the interfaces to be created in
the order they are created in the hypervisor. Renaming them
(particularly when some images are persistent, and some are not) is
confusing.
Secondly, it causes inconsistency, in that the Xen pv interfaces (for
instance) are ignored, whereas the kvm ones aren't.
Thirdly, it causes terrible problems (read unbootable machines) on old
Xen (and perhaps newer Xen), where the same interface appears twice -
once as an emulated HVM interface, and one as a PV on HVM interface each
with the same MAC address. That makes for confusion, particularly given
one subsystem is ignored and one isn't. Essentially the interfaces
constantly rename.
The (very easy) solution is to disable persistent net interface
renaming.
** Affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
https://bugs.launchpad.net/bugs/724601
Title:
UEC images should disable udev persistent net rules
--
Ubuntu-server-bugs mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
