yahoo-eng-team team mailing list archive

[James Falcon <1788972@xxxxxxxxxxxxxxxxxx>]

Tracked in Github Issues as https://github.com/canonical/cloud-
init/issues/3229

** Bug watch added: github.com/canonical/cloud-init/issues #3229
   https://github.com/canonical/cloud-init/issues/3229

** 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/1788972

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

Status in cloud-init:
  Expired

Bug description:
  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."

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1788972/+subscriptions