cloud-init should not treat MAC addresses as case sensitive
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Low
|
Unassigned |
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:
cloudinit/
Can you either fix the documentation to explicitly require lower case (this page has several uppe case references: https:/
description: | updated |
Changed in cloud-init: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in cloud-init: | |
assignee: | nobody → Brett Holman (holmanb) |
Changed in cloud-init: | |
assignee: | Brett Holman (holmanb) → nobody |
Hi,
Thanks for the bug report! I've filed bug 1876941 specifically for the documentation changes you suggested, and I'm going to rework this bug report slightly to cover fixing the underlying problem.
Dan