(re)starting networkd removes still-valid RFC 4941 ipv6 addrs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
I updated my Ubuntu 18.04.2 server from systemd 237-3ubuntu10.24 to 237-3ubuntu10.25. This caused a restart of systemd-networkd, breaking all TCP-over-IPv6 connections.
apt history entry:
Start-Date: 2019-08-06 19:46:21
Commandline: apt-get dist-upgrade -y
Requested-By: shivaram (1000)
Upgrade: libsystemd0:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), udev:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libudev1:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), systemd-sysv:amd64 (237-3ubuntu10.24, 237-3ubuntu10.25), libpam-
End-Date: 2019-08-06 19:54:17
systemd journal output:
Aug 06 19:47:40 pentos systemd[1]: Reloading.
Aug 06 19:47:57 pentos systemd[1]: Reexecuting.
Aug 06 19:47:58 pentos systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hie
Aug 06 19:47:58 pentos systemd[1]: Detected architecture x86-64.
Aug 06 19:47:58 pentos systemd[1]: Stopping Network Service...
Aug 06 19:47:58 pentos systemd[1]: Stopped Network Service.
Aug 06 19:47:58 pentos systemd[1]: Starting Network Service...
Aug 06 19:47:59 pentos systemd-
Aug 06 19:47:59 pentos systemd-
Aug 06 19:47:59 pentos systemd[1]: Started Network Service.
Aug 06 19:47:59 pentos systemd-
Aug 06 19:47:59 pentos systemd-
Aug 06 19:47:59 pentos dbus-daemon[947]: [system] Activating via systemd: service name='org.
Aug 06 19:47:59 pentos systemd-
summary: |
- updating bionic to 237-3ubuntu10.25 restarts systemd-networkd + (re)starting networkd removes still-valid RFC 4941 ipv6 addrs |
Changed in systemd (Ubuntu): | |
status: | Incomplete → Confirmed |
tags: | added: ddstreet |
upgrading systemd does restart networkd, but it should not remove any existing managed configuration while restarting (or stopping). For example:
ubuntu@lp1839231:~$ sudo systemctl start systemd-networkd MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 ff:fee8: e23f/64 scope link networkd. service, but it can still be activated by: networkd. socket MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 ff:fee8: e23f/64 scope link MULTICAST, UP,LOWER_ UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 ff:fee8: e23f/64 scope link
ubuntu@lp1839231:~$ ip a show ens3
2: ens3: <BROADCAST,
link/ether 52:54:00:e8:e2:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.122.25/24 brd 192.168.122.255 scope global dynamic ens3
valid_lft 3537sec preferred_lft 3537sec
inet6 fe80::5054:
valid_lft forever preferred_lft forever
ubuntu@lp1839231:~$ sudo systemctl stop systemd-networkd
Warning: Stopping systemd-
systemd-
ubuntu@lp1839231:~$ ip a show ens3
2: ens3: <BROADCAST,
link/ether 52:54:00:e8:e2:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.122.25/24 brd 192.168.122.255 scope global dynamic ens3
valid_lft 3529sec preferred_lft 3529sec
inet6 fe80::5054:
valid_lft forever preferred_lft forever
ubuntu@lp1839231:~$ sudo systemctl start systemd-networkd
ubuntu@lp1839231:~$ ip a show ens3
2: ens3: <BROADCAST,
link/ether 52:54:00:e8:e2:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.122.25/24 brd 192.168.122.255 scope global dynamic ens3
valid_lft 3599sec preferred_lft 3599sec
inet6 fe80::5054:
valid_lft forever preferred_lft forever
What specific config is in your networkd config files? What specific interface(s) or address(es) are you having trouble with?