Comment 6 for bug 1979277

@Lukas, thanks for looking into this. I agree that the call to io.netplan.Netplan.Apply is causing problems, but at the same I think that the script I wrote is wrong precisely because of the calls from the NM snap. The re-installs problem is the one that worries me: the wrapper in the NM snap calls Netplan.Apply only if the netplan config that sets NM as the default renderer does not exist, so NM should be restarted by netplan only once (after the restart the call to Apply would not happen again), and in any case networkctl should not show the eth as managed anymore. I will try some more debugging later to try to gather more details.