Comment 2 for bug 1919144

Hi @achilleasa,

Thanks for this, and have gotten around to test this today

I have, unfortunatley encountered a problem. When I have a seperate file in /etc/netplan with the extra configuration for netplan with link-local, adding the lxd machine fails, and the hypervisor loses all networking

Below is the log from the hypervisor (I added a password, and logged in manually after the fact, to get the details)
https://paste.ubuntu.com/p/kCs9CXdWWw/

Below is my juju model-config cloudinit-userdata
https://paste.ubuntu.com/p/prcc586HfY/

As you can see, I am adding an extra file called /etc/netplan/99-post-juju.yaml, and adding the link-local there.

But, when the lxd container is created, and the bridging re-done by juju, I get the following in /etc/netplan/99-juju.yaml

https://paste.ubuntu.com/p/SwfRh7K3h2/

Which is unexpected. I would expect it to combine the configs together.

Further on, when I add the link-local: [] to 50-cloud-init.yaml, after I have deployed it. juju does not respect the updated configuration, and the new configuration created as 99-juju.yaml will not have link-local, as shown below

root@as2-maas-node-06:/etc/netplan# grep link 99-juju.yaml
root@as2-maas-node-06:/etc/netplan# grep link 50-cloud-init.yaml.bak.1617018956
            link-local: []
            link-local: []
            link-local: []
            link-local: []
            link-local: []
            link-local: []
            link-local: []

Any thoughts on this would be appreciated

Happy to test this, as this is a local lab environment where I have deployed