canonical/cloud-init

cloud-init network config 2 rename does not match with name

Aperta

#3229 aperta il 11 mag 2023

 (3 commenti) (0 reazioni) (0 assegnatari)Python (1108 fork)auto 404
buggood first issuelaunchpad

Metriche repository

Star
 (3772 stelle)
Metriche merge PR
 (Metriche PR in attesa)

Descrizione

This bug was originally filed in Launchpad as LP: #1788972

Launchpad user Chaynika Saikia(csaikia) wrote on 2018-08-25T01:59:40.367027+00:00

Looking at the source code of cloud-init, when it tries to read a network configuration file, it looks for MAC address. Looking at the source code, it gives an impression that MAC address is a requirement to rename interfaces.

However, looking at this documentation, https://cloudinit.readthedocs.io/en/latest/topics/network-config-format-v2.html , it mentions that if I want to rename a network interface, I can use either name, macaddress or driver.

This is the most misleading part because, firstly, the source code does NOT search through 'name' and uses 'device_id' instead, whereas the documentation says: "name: <(scalar)>

Current interface name. Globs are supported, and the primary use case for matching on names, as selecting one fixed name can be more easily achieved with having no match: at all and just using the ID (see above). Note that currently only networkd supports globbing, NetworkManager does not."

Guida contributor