yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #82492
[Bug 1876363] [NEW] network-config macaddress needs to be lower case
Public bug reported:
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?
** Affects: cloud-init
Importance: Undecided
Status: New
--
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:
network-config macaddress needs to be lower case
Status in cloud-init:
New
Bug description:
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
Follow ups