[14:26] <mathsboy> hey I'm trying to help someone build a second network to a set of servers using netplan for the config. The config file is saved as /etc/netplan/00-config.yaml. My question is whether this filename should be something else? I have had a quick read of the docs and it seems like it should just be called config.yaml, otherwise the network won't persist after reboot. Is that correct?
[14:27] <mathsboy> oh wait, no...  *.yaml is considered
[14:30] <slyon> righ. any *.yaml is accepted, where higher name overrides the lower name
[15:35] <mathsboy> hmm, so any ideas where I should look to figure out why the config doesn't load after rebooting? It works fine if I netplan apply, but I'd like it to start automatically...
[15:36] <slyon> mathsboy: does "netplan --debug apply" give any hints?
[15:36] <slyon> maybe you could share/pastebin your YAML config somewhere so we can have a look at it?
[15:37] <slyon> do you see netplan configuration files generated after boot in /run/systemd/network and/or /run/NetworkManager/system-connections ?
[15:58] <mathsboy> oh good questions... I will check and come back
[15:59] <mathsboy> okay! it has a permission denied
[16:00] <mathsboy> whenn it tries to create the file in /etc/systemd
[16:00] <mathsboy> sorry run/systemd/network
[16:15] <slyon> the netplan generator should run as root during bootup. otherwise your system might be utterly broken..
[16:25] <mathsboy> yeah, utterly broken wouldn't be a huge surprise at this point. Here's a pastebin with the config and output of --debug apply: https://pastebin.com/p2ikcWhH