Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/4043
** Bug watch added: github.com/canonical/cloud-init/issues #4043 https://github.com/canonical/cloud-init/issues/4043 ** Changed in: cloud-init Status: Triaged => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1996789 Title: Don't Break On Duplicate Mac Addresses Status in cloud-init: Expired Bug description: Currently when duplicate mac addresses are detected, cloud-init dies. While duplicate macs are typically corner cases, there are cases when they can be valid[1]. Consider this example[2]. After bonding two interfaces, the interfaces were left with duplicate mac addresses. Using cloud-init on this system fails at the time that these devices are detected. If no network config is given, or if a config is given configuring a single address, we have the opportunity to do something intelligent to allow cloud-init to boot by using the "fallback interface" (in cloud- init this is the first interface), rather than throwing an exception and dying. Netplan's mac matching assumes 1:1 mapping between mac addresses and interfaces, so in the case of multiple interfaces configured with matches, we still can't do anything intelligent. [1] Until these have unique addresses, these interfaces will not be usable on the same broadcast domain, but they should still be able to work individually on different networks. [2] https://stackoverflow.com/questions/74459180/deleted-bond-interface-left-me-with-duplicate-mac-on-two-interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1996789/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
