** Description changed:
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
** Changed in: cloud-init (Ubuntu)
Status: Incomplete = Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Thanks for reporting this bug, is this and bugs 726635 both duplicates
of the same issue demonstrated differently?
** Changed in: cloud-init (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
No, these are different bugs I think, though they relate to the same
sort of issue.
Bug 726635 says that even on conventional (non-UEC) images, MAC
addresses ranges used by Virtualbox should be ignored in the persistent
udev rules. That's fair enough, though I note Xen and KVM were treated
From the manpage of udev: Rule files are required to have a unique
name, duplicate file names are ignored. Files in /etc/udev/rules.d/ have
precedence over files with the same name in /lib/udev/rules.d/. This can
be used to ignore a default rules file if needed..
Untested, but perhaps on UEC
Further example of why this is needed: see my comment on Bug 726635.
VirtualBox appears to use a borrowed MAC range, rather than an
officiant assignment. That means it's probably not a great idea to use
that MAC address range as a basis for black/whitelisting.
--
You received this bug
