| 2016-06-20 19:44:22 |
Scott Moser |
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 |
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:
* bug 1579130: need to support renaming of devices in container and on first boot |
|
