Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3672
** Bug watch added: github.com/canonical/cloud-init/issues #3672 https://github.com/canonical/cloud-init/issues/3672 ** 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/1876363 Title: cloud-init should not treat MAC addresses as case sensitive Status in cloud-init: Expired Bug description: Currently, cloud-init can run into issues applying network configuration if the MAC addresses reported by the system are in a different case to the MAC addresses provided by the network configuration source. It is likely that there are also other places where a mismatch could happen. We should ensure that cloud-init's MAC address handling is not case sensitive. [Original Report] I'm using an ISO with the following yaml in network-config. cloud-init will not match eth0, but will match eth1 due to capitalization. version: 2 ethernets: eth0: match: macaddress: 00:15:5D:0E:AE:0C set-name: External eth1: match: macaddress: 00:15:5d:0e:ae:0d set-name: Internal RuntimeError: Not all expected physical devices present: {'00:15:5D:0E:AE:0C'} cloudinit/net/__init__.py, Line 545, in wait_for_physdevs. Can you either fix the documentation to explicitly require lower case (this page has several uppe case references: https://cloudinit.readthedocs.io/en/latest/topics/network-config- format-v2.html). Or do the lower case conversion in wait_for_physdevs when you compare the present_macs to the expected_macs? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1876363/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
