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]: enp161s0f1np1: Re-configuring with /run/systemd/network/10-netplan-n2p2.network systemd-networkd[2352]: lan_si: Re-configuring with /run/systemd/network/10-netplan-lan_si.network systemd-networkd[2352]: eno1: Re-configuring with /run/systemd/network/10-netplan-zzz-all-en.network systemd-networkd[2352]: wan: Re-configuring with /run/systemd/network/10-netplan-wan.network systemd-networkd[2352]: bond_wan: Re-configuring with /run/systemd/network/10-netplan-bond_wan.network systemd-networkd[2352]: eno2: Re-configuring with /run/systemd/network/10-netplan-zzz-all-en.network systemd-networkd[2352]: lan_mgmnt: Re-configuring with /run/systemd/network/10-netplan-lan_mgmnt.network systemd-networkd[2352]: eno33np0: Re-configuring with /run/systemd/network/10-netplan-n1p1.network systemd-networkd[2352]: eno34np1: Re-configuring with /run/systemd/network/10-netplan-n1p2.network systemd-networkd[2352]: bond_lan: Re-configuring with /run/systemd/network/10-netplan-bond_lan.network systemd-networkd[2352]: enp161s0f0np0: Re-configuring with /run/systemd/network/10-netplan-n2p1.network systemd-networkd[2352]: enp161s0f1np1: Link DOWN systemd-networkd[2352]: enp161s0f1np1: Lost carrier systemd-networkd[2352]: enp161s0f1np1: Re-configuring with /run/systemd/network/10-netplan-n2p2.network systemd-networkd[2352]: eno2: Re-configuring with /run/systemd/network/10-netplan-zzz-all-en.network systemd[1]: Condition check resulted in OpenVSwitch configuration for cleanup being skipped. chronyd[17235]: Source 10.160.4.2 offline chronyd[17235]: Source 10.160.4.1 offline kernel: bond_wan: (slave enp161s0f0np0): link status definitely down, disabling slave kernel: bond_wan: now running without any active interface! kernel: bond_wan: (slave eno33np0): link status definitely down, disabling slave kernel: bond_lan: (slave enp161s0f1np1): link status definitely down, disabling slave kernel: bond_lan: (slave eno34np1): link status definitely down, disabling slave kernel: bond_lan: now running without any active interface! systemd-networkd[2352]: enp161s0f0np0: Re-configuring with /run/systemd/network/10-netplan-n2p1.network systemd-networkd[2352]: eno34np1: Re-configuring with /run/systemd/network/10-netplan-n1p2.network systemd-networkd[2352]: eno33np0: Re-configuring with /run/systemd/network/10-netplan-n1p1.network systemd-networkd[2352]: eno33np0: Link DOWN systemd-networkd[2352]: eno33np0: Lost carrier systemd-networkd[2352]: eno1: Re-configuring with /run/systemd/network/10-netplan-zzz-all-en.network systemd-networkd[2352]: eno34np1: Link DOWN systemd-networkd[2352]: eno34np1: Lost carrier systemd-networkd[2352]: bond_wan: Re-configuring with /run/systemd/network/10-netplan-bond_wan.network systemd-networkd[2352]: bond_lan: Re-configuring with /run/systemd/network/10-netplan-bond_lan.network systemd-networkd[2352]: enp161s0f0np0: Link DOWN systemd-networkd[2352]: enp161s0f0np0: Lost carrier systemd-networkd[2352]: lan_si: Re-configuring with /run/systemd/network/10-netplan-lan_si.network systemd-networkd[2352]: wan: Re-configuring with /run/systemd/network/10-netplan-wan.network systemd-networkd[2352]: lan_mgmnt: Re-configuring with /run/systemd/network/10-netplan-lan_mgmnt.network systemd-networkd[2352]: bond_wan: Lost carrier systemd-networkd[2352]: wan: Lost carrier systemd-networkd[2352]: bond_lan: Lost carrier systemd-networkd[2352]: lan_mgmnt: Lost carrier systemd-networkd[2352]: lan_si: Lost carrier kernel: mlx5_core 0000:a1:00.1 enp161s0f1np1: Link up kernel: 8021q: adding VLAN 0 to HW filter on device enp161s0f1np1 kernel: mlx5_core 0000:63:00.0 eno33np0: Link up kernel: 8021q: adding VLAN 0 to HW filter on device eno33np0 kernel: mlx5_core 0000:63:00.1 eno34np1: Link up kernel: 8021q: adding VLAN 0 to HW filter on device eno34np1 kernel: mlx5_core 0000:a1:00.0 enp161s0f0np0: Link up kernel: 8021q: adding VLAN 0 to HW filter on device enp161s0f0np0 systemd-networkd[2352]: enp161s0f1np1: Link UP kernel: bond_lan: (slave enp161s0f1np1): link status definitely up, 10000 Mbps full duplex kernel: bond_lan: active interface up! kernel: bond_lan: (slave eno34np1): link status definitely up, 10000 Mbps full duplex kernel: bond_wan: (slave enp161s0f0np0): link status definitely up, 10000 Mbps full duplex kernel: bond_wan: active interface up! kernel: bond_wan: (slave eno33np0): link status definitely up, 10000 Mbps full duplex systemd-networkd[2352]: enp161s0f1np1: Gained carrier systemd-networkd[2352]: eno33np0: Link UP systemd-networkd[2352]: eno33np0: Gained carrier systemd-networkd[2352]: eno34np1: Link UP systemd-networkd[2352]: eno34np1: Gained carrier systemd-networkd[2352]: enp161s0f0np0: Link UP systemd-networkd[2352]: enp161s0f0np0: Gained carrier systemd-networkd[2352]: bond_lan: Gained carrier systemd-networkd[2352]: lan_mgmnt: Gained carrier systemd-networkd[2352]: lan_si: Gained carrier systemd-networkd[2352]: bond_wan: Gained carrier systemd-networkd[2352]: wan: Gained carrier chronyd[17235]: Source 10.160.4.2 online chronyd[17235]: Source 10.160.4.1 online -- 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, heartbeat, corosync, pacemaker (interface aliases are restarted) Status in netplan: Incomplete Status in heartbeat package in Ubuntu: Won't Fix Status in keepalived package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Status in keepalived source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in keepalived source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Status in keepalived source package in Focal: Confirmed Status in systemd source package in Focal: Fix Released Bug description: [impact] - ALL related HA software has a small problem if interfaces are being managed by systemd-networkd: nic restarts/reconfigs are always going to wipe all interfaces aliases when HA software is not expecting it to (no coordination between them. - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is smarter in this case because it has a service monitor that will restart the virtual IP resource, in affected node & nic, before considering a real failure, but other HA service might consider a real failure when it is not. [test case] - comment #14 is a full test case: to have 3 node pacemaker, in that example, and cause a networkd service restart: it will trigger a failure for the virtual IP resource monitor. - other example is given in the original description for keepalived. both suffer from the same issue (and other HA softwares as well). [regression potential] - this backports KeepConfiguration parameter, which adds some significant complexity to networkd's configuration and behavior, which could lead to regressions in correctly configuring the network at networkd start, or incorrectly maintaining configuration at networkd restart, or losing network state at networkd stop. - Any regressions are most likely to occur during networkd start, restart, or stop, and most likely to involve missing or incorrect ip address(es). - the change is based in upstream patches adding the exact feature we needed to fix this issue & it will be integrated with a netplan change to add the needed stanza to systemd nic configuration file (KeepConfiguration=) [other info] original description: --- Configure netplan for interfaces, for example (a working config with IP addresses obfuscated) network: ethernets: eth0: addresses: [192.168.0.5/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth2: addresses: - 12.13.14.18/29 - 12.13.14.19/29 gateway4: 12.13.14.17 dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth3: addresses: [10.22.11.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth4: addresses: [10.22.14.6/24] dhcp4: false nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] eth7: addresses: [9.5.17.34/29] dhcp4: false optional: true nameservers: search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, phone.blah.com] addresses: [10.22.11.1] version: 2 Configure keepalived (again, a working config with IP addresses obfuscated) global_defs # Block id { notification_email { sysadm...@blah.com } notification_email_from keepali...@system3.hq.blah.com smtp_server 10.22.11.7 # IP smtp_connect_timeout 30 # integer, seconds router_id system3 # string identifying the machine, # (doesn't have to be hostname). vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18 vrrp_mcast_group6 ff02::12 # optional, default ff02::12 enable_traps # enable SNMP traps } vrrp_sync_group collection { group { wan lan phone } vrrp_instance wan { state MASTER interface eth2 virtual_router_id 77 priority 150 advert_int 1 smtp_alert authentication { auth_type PASS auth_pass BlahBlah } virtual_ipaddress { 12.13.14.20 } } vrrp_instance lan { state MASTER interface eth3 virtual_router_id 78 priority 150 advert_int 1 smtp_alert authentication { auth_type PASS auth_pass MoreBlah } virtual_ipaddress { 10.22.11.13/24 } } vrrp_instance phone { state MASTER interface eth4 virtual_router_id 79 priority 150 advert_int 1 smtp_alert authentication { auth_type PASS auth_pass MostBlah } virtual_ipaddress { 10.22.14.3/24 } } At boot the affected interfaces have: 5: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ab:cd:ef:90:c0:e3 brd ff:ff:ff:ff:ff:ff inet 10.22.14.6/24 brd 10.22.14.255 scope global eth4 valid_lft forever preferred_lft forever inet 10.22.14.3/24 scope global secondary eth4 valid_lft forever preferred_lft forever inet6 fe80::ae1f:6bff:fe90:c0e3/64 scope link valid_lft forever preferred_lft forever 7: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ab:cd:ef:b0:26:29 brd ff:ff:ff:ff:ff:ff inet 10.22.11.6/24 brd 10.22.11.255 scope global eth3 valid_lft forever preferred_lft forever inet 10.22.11.13/24 scope global secondary eth3 valid_lft forever preferred_lft forever inet6 fe80::ae1f:6bff:feb0:2629/64 scope link valid_lft forever preferred_lft forever 9: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ab:cd:ef:b0:26:2b brd ff:ff:ff:ff:ff:ff inet 12.13.14.18/29 brd 12.13.14.23 scope global eth2 valid_lft forever preferred_lft forever inet 12.13.14.20/32 scope global eth2 valid_lft forever preferred_lft forever inet 12.33.89.19/29 brd 12.13.14.23 scope global secondary eth2 valid_lft forever preferred_lft forever inet6 fe80::ae1f:6bff:feb0:262b/64 scope link valid_lft forever preferred_lft forever Run 'netplan try' (didn't even make any changes to the configuration) and the keepalived addresses disappear never to return, the affected interfaces have: 5: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ab:cd:ef:90:c0:e3 brd ff:ff:ff:ff:ff:ff inet 10.22.14.6/24 brd 10.22.14.255 scope global eth4 valid_lft forever preferred_lft forever inet6 fe80::ae1f:6bff:fe90:c0e3/64 scope link valid_lft forever preferred_lft forever 7: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ab:cd:ef:b0:26:29 brd ff:ff:ff:ff:ff:ff inet 10.22.11.6/24 brd 10.22.11.255 scope global eth3 valid_lft forever preferred_lft forever inet6 fe80::ae1f:6bff:feb0:2629/64 scope link valid_lft forever preferred_lft forever 9: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether ab:cd:ef:b0:26:2b brd ff:ff:ff:ff:ff:ff inet 12.13.14.18/29 brd 12.13.14.23 scope global eth2 valid_lft forever preferred_lft forever inet 12.33.89.19/29 brd 12.13.14.23 scope global secondary eth2 valid_lft forever preferred_lft forever inet6 fe80::ae1f:6bff:feb0:262b/64 scope link valid_lft forever preferred_lft forever To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1815101/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
