[Bug 1811868] Re: networkd/NetworkManager are not re-started on netplan apply when config files are removed
Launchpad Bug Tracker
1811868 at bugs.launchpad.net
Wed May 8 00:00:42 UTC 2019
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---------------
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
pass; it breaks "default" renderer behavior when multiple files may set
a global renderer and expect the last to take effect globally.
(LP: #1825206)
* debian/patches/git_reorg_netdef_validation_181b583.patch: correct the
fallout from the above change: validate netdefs in a single pass at the
very end of parsing, once we know which is the applicable renderer. This
makes sure tunnels get validated correctly.
netplan.io (0.96-0ubuntu0.18.04.3) bionic; urgency=medium
* debian/patches/disable-networkd-tunnels-ipip-gre.patch: disable IPIP and
GRE tunnel tests; those appear to be broken because neither the kernel nor
networkd bring up the device automatically as in other releases.
netplan.io (0.96-0ubuntu0.18.04.2) bionic; urgency=medium
* d/p/0001-Partially-revert-the-change-for-enabling-systemd-net.patch:
Partially revert changes to networkd jobs ordering: leave systemd-networkd
enabled in multi-user.target instead of network-online.target, as in some
minimal setups there might be no job requiring network-online.target,
whereas the natural target to reach for booting is multi-user.target.
(LP: #1821867)
netplan.io (0.96-0ubuntu0.18.04.1) bionic; urgency=medium
* Backport netplan.io 0.96 to 18.04.
* debian/patches/glib_changes.patch: Patch tests to work again on older GLib.
* debian/control: adjust Depends for bionic / re-add nplan package.
netplan.io (0.96-0ubuntu1) disco; urgency=medium
* New upstream release 0.96.
- Moved netplan-wpa@ services to earlier at boot (LP: #1819014)
- Restart services when unconfiguring (LP: #1811868)
- Use the .nmconnection extension for NM keyfiles (LP: #1817655)
- Fixed integration tests runner to correctly report failures
- Enforce integrity for use-routes in networkd backend.
- Ensure terminal state at end of test (LP: #1817660)
- Various small test fixes.
- Fix typos in documentation.
* debian/control: Update Maintainer for ubuntu upload.
netplan.io (0.95-2) unstable; urgency=medium
* Set Priority to optional (Closes: #920327).
netplan.io (0.95-1) unstable; urgency=medium
* New upstream release.
* Update autopkgtests from the upstream.
* Add debian/watch following GitHub releases.
* Add Homepage (Closes: #917233).
netplan.io (0.95) disco; urgency=medium
* New upstream release:
- Added support for WPA Enterprise / 802.1x authentication (LP: #1739578)
- Added support for setting up IP tunnels; supporting the types: ipip,
gretap, VTI, ISATAP (NetworkManager only), sit, gre, ipip6 and ip6ip6.
+ Fixes sit (ipv6) tunnels using Hurricane Electric (LP: #1799487)
- Add support to override networkd UseMTU setting (LP: #1807273)
- Generate output files in dependency order
- Refactored unit and integration tests, along with various cleanups.
- Add DHCP overrides to control route usage and default metric for DHCP
routes. (LP: #1776228)
- Mitigate against bad matching on devices behind bonds then they share
the same MAC from a physical interface. (LP: #1804861)
- Added snapcraft.yaml.
netplan.io (0.90.1) disco; urgency=medium
* Do not assume /etc/network exists in postinst, as netbase 5.5 no longer
creates it.
* netplan/cli/commands/ip.py: fix a flake.
netplan.io (0.90) disco; urgency=medium
* New upstream release:
- build: fixes for building on RPM-based distros
- build: code prettiness changes (make indentation consistent)
- Fix device name-changes detection (LP: #1770082)
- Add support for IPv6 Privacy Extensions (LP: #1750392)
- Add dhcp{4,6}-overrides to control DNS, NTP, hostname updates via DHCP
(LP: #1759014)
- Clarify MAC and MTU setting requirements (LP: #1800668)
- Various documentation fixes (LP: #1800669)
- Improve error reporting to give clearer messages and context
(LP: #1800670)
- Skip non-physical/bond interfaces when applying renames (LP: #1802322)
netplan.io (0.40.2-1) unstable; urgency=medium
* Upload to Debian (Closes: #882661).
netplan.io (0.40.2) cosmic; urgency=medium
* tests/integration.py: Mark regexes with r to pacify pycodestyle's
W605.
-- Mathieu Trudel-Lapierre <cyphermox at ubuntu.com> Fri, 26 Apr 2019
15:19:47 -0400
** Changed in: netplan.io (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: netplan.io (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1811868
Title:
networkd/NetworkManager are not re-started on netplan apply when
config files are removed
Status in netplan:
Fix Released
Status in netplan.io package in Ubuntu:
Fix Released
Status in netplan.io source package in Bionic:
Fix Released
Status in netplan.io source package in Cosmic:
Fix Released
Bug description:
[Impact]
All users of netplan when changing configuration and removing devices.
[Test case]
1) Set up a configuration with additiona devices:
network:
version: 2
ethernets:
eno1:
match:
macaddress: 78:45:c4:ef:b6:39
mtu: 1500
set-name: eno1
eno2:
match:
macaddress: 78:45:c4:ef:b6:3b
mtu: 1500
set-name: eno2
eno3:
match:
macaddress: 78:45:c4:ef:b6:3d
mtu: 1500
set-name: eno3
eno4:
match:
macaddress: 78:45:c4:ef:b6:3f
mtu: 1500
set-name: eno4
enp4s0f0:
match:
macaddress: 00:0a:f7:72:a7:28
mtu: 9000
set-name: enp4s0f0
enp4s0f1:
match:
macaddress: 00:0a:f7:72:a7:2a
mtu: 9000
set-name: enp4s0f1
enp5s0f0:
match:
macaddress: 00:0e:1e:ac:67:00
mtu: 9000
set-name: enp5s0f0
enp5s0f1:
match:
macaddress: 00:0e:1e:ac:67:02
mtu: 9000
set-name: enp5s0f1
bonds:
bond0:
interfaces:
- enp4s0f0
- enp5s0f0
macaddress: 52:54:45:7f:7b:6f
mtu: 9000
parameters:
down-delay: 0
lacp-rate: fast
mii-monitor-interval: 100
mode: 802.3ad
transmit-hash-policy: layer3+4
up-delay: 0
bond1:
interfaces:
- enp4s0f1
- enp5s0f1
macaddress: 52:54:45:26:cb:7b
mtu: 9000
parameters:
down-delay: 0
lacp-rate: fast
mii-monitor-interval: 100
mode: 802.3ad
transmit-hash-policy: layer3+4
up-delay: 0
bondm:
addresses:
- 10.20.0.84/24
gateway4: 10.20.0.1
interfaces:
- eno1
- eno2
- eno3
- eno4
macaddress: 52:54:45:7e:d0:7f
mtu: 1500
nameservers:
addresses:
- 10.20.0.14
- 10.20.0.10
- 10.20.0.11
- 10.20.0.12
search:
- maas
parameters:
down-delay: 0
lacp-rate: fast
mii-monitor-interval: 100
mode: 802.3ad
transmit-hash-policy: layer3+4
up-delay: 0
vlans:
bond0.804:
addresses:
- 10.20.16.50/24
id: 804
link: bond0
mtu: 1500
nameservers: &id001
addresses:
- 10.20.0.14
- 10.20.0.10
- 10.20.0.11
- 10.20.0.12
search:
- maas
bond0.805:
addresses:
- 10.20.20.50/24
id: 805
link: bond0
mtu: 1500
nameservers: *id001
bond0.807:
addresses:
- 10.20.28.2/24
id: 807
link: bond0
mtu: 9000
nameservers: *id001
bond0.808:
addresses:
- 10.20.32.50/24
id: 808
link: bond0
mtu: 9000
nameservers: *id001
bond0.810:
addresses:
- 10.20.33.2/29
id: 810
link: bond0
mtu: 1500
nameservers: *id001
2) Run 'netplan apply' to configure the devices.
3) Verify bond0, bond1, bondm devices are created.
4) Configure netplan again:
network:
version: 2
renderer: NetworkManager
5) Run 'netplan apply'
6) Verify that the daemons are restarted, and devices are deconfigured (this may not mean the devices are removed).
[Regression potential]
Pay attention to issues with network connectivity caused by the restarting of daemons, or any other issues that could potentially be caused by the fact that the backend daemons are being restarted when configurations have been removed.
---
The network managers networkd/NetworkManager are re-started on
"netplan apply" when there are files created by netplan in the
corresponding /run/* folder.
However, if we change from a configuration in which we have config
files in /run to one where we remove those files, the services are not
re-started. For instance, if we switch from a configuration in which
some devices are managed by networkd to one in which all devices are
managed by NM, networkd is not re-started, so it still thinks it
should manage those devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1811868/+subscriptions
More information about the foundations-bugs
mailing list