I think fix will be released in systemd 253.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1815101
Title:
[master] Restarting systemd-networkd breaks keepalived, heartbea
I did report to systemd: https://github.com/systemd/systemd/issues/25067
As for timestamps, systemd-networkd does not do any weird things when
timestamps change on non-bridge interfaces.
** Bug watch added: github.com/systemd/systemd/issues #25067
https://github.com/systemd/systemd/issues/2506
It is reproducible on a VM with a simple netplan file with only one
ethernet and one bond interface:
network:
ethernets:
n1p1:
match:
name: ens192
bonds:
bond_all:
interfaces:
- n1p1
parameters:
I do not see any difference.
However I am not convinced that this is not a networkd issue anyway... here are
journal logs from `netplan apply`, where n1p1, n1p2 are first and second port
of first network card, n2p2, n2p2 for second network card:
systemd[1]: Reloading.
systemd-networkd[2352]: enp
Hi!
I am having trouble making this work in graceful manner.
Fresh Ubuntu 22.04, systemd 249.11-0ubuntu3.6, netplan 0.104-0ubuntu2.1.
Host has multiple interfaces (6 physical, 2 bonds, 3 vlans on those bonds) and
multiple (20 to 30) IP addresses on those vlan interfaces.
EVERY time i issue `netp
5 matches
Mail list logo