Reverting duplicate to make the conclusion for this bug clearer:
This file belongs in NM and NM is supposed to make sure that it doesn't
break things (which is why there is a bug for upgrade as bug 1676547).
It should not be seen as an override but as Ubuntu shipping a default
configuration meant to work on the majority of systems (see below).
nplan is in standard and on all systems, whereas NM doesn't normally
exist on servers. nplan should not leave unnecessary files around -- on
servers, the file in /usr/lib would be unnecessary -- it only makes
sense if NetworkManager is installed.
On a typical desktop new install, netplan and NM would be installed,
netplan would start at boot and write an override file to
/run/NetworkManager/conf.d (as per its default configuration) to tell NM
to manage all files. The networking behavior expected by our users would
be maintained (ie. they don't need to run netplan, but we want to make
it available and start educating on its use).
On earlier installed desktop systems, netplan gets installed on upgrade
but likely does not start at boot (and regardless should not break
networking before a reboot happens) and NM should write its "default
config" and override it via /etc/NetworkManager/conf.d/10-globally-
managed-devices.conf by postinst on its own upgrade. This is done to
ensure networking is not broken during upgrade, and that old behavior is
maintained on upgraded systems.
On servers, netplan is installed but not NetworkManager. netplan should
not add unnecessary files to the install. Default behavior should
already be maintained because the empty configuration shipped by default
will not affect ifupdown/networkd; but users can start using netplan to
configure their systems instead of ifupdown immediately.
The intent here is to make sure that NM behaves the right way given that
nplan is on all systems, and that it does so following whether netplan
is in use or not (as much as possible). netplan is meant to replace
ifupdown for static network configuration, and to configure
NetworkManager or networkd (depending on what is available)
appropriately to drive the networking story requested by the user.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: nplan (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1673625
Title:
10-globally-managed-devices.conf contained in wrong package
Status in network-manager package in Ubuntu:
Won't Fix
Status in nplan package in Ubuntu:
Won't Fix
Bug description:
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is
installed from network-manager but without nplan it has no benefit,
and breaks networking until you override it. Since the config is
there to change how NetworkManager behaves in the presence of nplan,
the configuration file itself should actually be contained in the
nplan package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1673625/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
