diff options
| author | Scott Moser <smoser@ubuntu.com> | 2016-06-20 17:10:45 -0400 |
|---|---|---|
| committer | Scott Moser <smoser@ubuntu.com> | 2016-06-20 17:10:45 -0400 |
| commit | e6b594bf2bf4cd40bbfbe9581c2b62f3b77e9123 (patch) | |
| tree | c67eaf601903947d866fe5d2bfdc9e8078927f4d /cloudinit/config | |
| parent | 776b0cfe847f531d8d5a235f52673c3da1f06064 (diff) | |
| parent | 4fc10ef3f349e6280e2002d980c4c63e6a741d2f (diff) | |
| download | vyos-cloud-init-e6b594bf2bf4cd40bbfbe9581c2b62f3b77e9123.tar.gz vyos-cloud-init-e6b594bf2bf4cd40bbfbe9581c2b62f3b77e9123.zip | |
do not render systemd.link files
When fixing bug 1579130, we made cloud-init rename devices itself,
rather than relying on the systemd.link files to do that.
That was necessary to
- rename devices in a container
- rename devices on first boot or in any situation when the
link files in the initramfs were stale.
However, 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.
Also added here is a header into the rendered ENI file:
/etc/network/interfaces.d/50-cloud-init.cfg
that describes how to disable cloud-init networking.
LP: #1594546
Diffstat (limited to 'cloudinit/config')
0 files changed, 0 insertions, 0 deletions