** Description changed: + [Impact] + netplan users on Ubuntu Core systems wishing to change netplan configuration that affects NetworkManager + + [Test cases] + 1) Run 'sudo netplan apply' + 2) Verify that NetworkManager has been restarted, and no errors were shown on console. + + [Regression potential] + This fixes a current regression where netplan fails to use the right NetworkManager service file to restart NM on Ubuntu Core systems. On systems with both the NetworkManager from the Ubuntu archive and a snap-based NetworkManager are installed, this would default to the snap-based NetworkManager. In these cases, existing systems would regress in behavior if they have a working installation of NetworkManager from the Ubuntu archive. + + --- + A previous code change seems to have been dropped from nplan on xenial. The change enabled netplan to restart network-manager service when netman is installed as a snap. Without the change, netplan tries to restart the debian packaged service name of netman. Here is the change: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1627641/comments/16 Please also see customer's fourm post on this topic: https://forum.snapcraft.io/t/netplan-and-networkmanager-interaction-bug/3863
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747714 Title: network manager snap service name regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1747714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
