yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

Public bug reported:

When fixing bug 1579130 , we made cloud-init rename devices itself,
rather than relying on the systemd.link files to do that.

cloud-init was still writing .link files like:
 /etc/systemd/network/50-cloud-init-ens2.link

That leads to just a confusing situation as cloud-init will trump
any renaming systemd does in all cases.

We'd like to get to a place where cloud-init allows the user to later customize
the name of the devices in a supported manner, but for the moment, these files
only create confusion.

Related Bugs:
 * 1579130:  need to support renaming of devices in container and on first boot

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

Title:
  no need to write systemd.link files

Status in cloud-init:
  New

Bug description:
  When fixing bug 1579130 , we made cloud-init rename devices itself,
  rather than relying on the systemd.link files to do that.

  cloud-init was still writing .link files like:
   /etc/systemd/network/50-cloud-init-ens2.link

  That leads to just a confusing situation as cloud-init will trump
  any renaming systemd does in all cases.

  We'd like to get to a place where cloud-init allows the user to later customize
  the name of the devices in a supported manner, but for the moment, these files
  only create confusion.

  Related Bugs:
   * 1579130:  need to support renaming of devices in container and on first boot

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