Comment 2 for bug 1713226

this was a upgrade so the ifupdown problem should not happen with clean installs.
How is the migration planned?

If for example one will do a upgrade from 16.04 to the next 18.04 such problems are a clear show stopper since breaking the network for most servers will mean needing physical access.

On my system there is nothing that puts the interface to state up, so I blame systemd-networkd being it (normal desktop system, so /etc/network/interfaces contains only a lo entry).
But after all I consider having two systems that configure the same set of network interfaces will never work reliable.
I think the best would be systemd-networkd.service conflicts network-manager.service

What is the pro of enabling systemd-networkd on desktop systems? I see advantages on server systems over ifupdown, but afaik neither gnome nor plasma has systemd-networkd integration.