[Bug 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly
Dan Streetman
dan.streetman at canonical.com
Wed Apr 10 21:13:17 UTC 2019
autopkgtest regressions:
bionic:
apt passed on re-run
dovecot (armhf) failed again; i'm re-running it again, but i think we
can ignore it as it failed in the same way for the openssl upload before
we uploaded this.
snapd i opened bug 1824237, although that might be limited to only
cosmic, not bionic
all other bionic tests ignorable as explained in previous comments
cosmic:
snapd as with bionic, bug 1824237
docker.io tests fail also due to bug 1824237 (because they use snaps in their tests, and the core snap is broken)
systemd test are failing, i think, also because of bug 1824237. since
the problem is the cosmic 'core' snap is broken, all other snaps fail,
and the failing test for all systemd archs is 'boot-and-services' which
checks that no services failed. it appears some of the services, like
lxd, because they could not start due to broken core snap; i'm testing
locally to verify this.
all other cosmic tests ignorable as explained in previous comments
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1818282
Title:
systemd-networkd - RoutingPolicyRule does not apply correctly
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Fix Committed
Status in systemd source package in Cosmic:
Fix Committed
Status in systemd source package in Disco:
Fix Released
Status in systemd package in Debian:
Fix Committed
Bug description:
[Impact]
When attaching multiple IPs on secondary interface the routing policy rules do not
apply for all IPs.
The rules that are applied after restarting networkd are random.
The issue has been reported and addressed upstream.
[Test Case]
Attach multiple IPs to secondary interface, config file:
$ cat /etc/systemd/network/ens8.network
[Match]
Name=ens8
[Network]
Address=172.31.28.195/20
Address=172.31.24.151/20
Address=172.31.24.152/20
Address=172.31.24.153/20
[Route]
Destination=0.0.0.0/0
Gateway=172.31.16.1
Table=1000
[Route]
Destination=172.31.24.153
Gateway=0.0.0.0
Scope=link
Table=1000
[Route]
Destination=172.31.28.195
Gateway=0.0.0.0
Scope=link
Table=1000
[Route]
Destination=172.31.24.151
Gateway=0.0.0.0
Scope=link
Table=1000
[Route]
Destination=172.31.24.152
Gateway=0.0.0.0
Scope=link
Table=1000
[RoutingPolicyRule]
From=172.31.24.153
Table=1000
[RoutingPolicyRule]
From=172.31.28.195
Table=1000
[RoutingPolicyRule]
From=172.31.24.152
Table=1000
[RoutingPolicyRule]
From=172.31.24.151
Table=1000
$ ip rule show
0: from all lookup local
0: from 172.31.24.151 lookup 1000
32766: from all lookup main
32767: from all lookup default
- restart networkd
$ sudo systemctl restart systemd-networkd
$ ip rule show
0: from all lookup local
0: from 172.31.24.151 lookup 1000
0: from 172.31.24.153 lookup 1000
0: from 172.31.28.195 lookup 1000
32766: from all lookup main
32767: from all lookup default
- restart again
$ sudo systemctl restart systemd-networkd
$ ip rule show
0: from all lookup local
0: from 172.31.24.151 lookup 1000
0: from 172.31.24.152 lookup 1000
32766: from all lookup main
32767: from all lookup default
The behaviour is random
[Regression Potential]
May impact the systemd-networkd service functionality.
[Other]
Affects Disco Bionic and Cosmic.
Upstream bug : https://github.com/systemd/systemd/issues/11280
Upstream fix : https://github.com/systemd/systemd/pull/11795/commits
$ lsb_release -rd
Description: Ubuntu Disco Dingo (development branch)
Release: 19.04
Systemd version :
systemd:
Installed: 240-6ubuntu1
Candidate: 240-6ubuntu1
Version table:
*** 240-6ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818282/+subscriptions
More information about the foundations-bugs
mailing list