After crushing the logs a bit more, I found a few interesting things and also have a few open questions. Thank you very much for your `date` timestamps in between the different steps, those are very helpful in linking the order of events!
Open questions: 1) The "udevadm-monitor.txt" log shows that there is a manual "/etc/systemd/network/10-enP53p0s0.link" configuration file, while all other interfaces make use of "/usr/lib/systemd/network/99-default.link". Can you show us what is inside this file? 2) In comment #22 you show the output of "networkctl": root@ilabg13:~# netplan apply root@ilabg13:~# networkctl status enP53p0s0.171 --no-pager ? 7: enP53p0s0.171 Link File: n/a Network File: n/a Type: vlan State: degraded (pending) HW Address: 82:0c:9b:c9:78:f8 => I wonder why "Link File: n/a" and "Network File: n/a" is set.. The Link state is still "(pending)", would you mind executing the same steps again and re-executing the "networkctl status enP53p0s0.171 --no-pager" a bit later again (like 10sec after and 30sec after)? 3) Does the workaround from https://github.com/systemd/systemd/issues/15445#issuecomment-776856604 work for you? E.g.: # netplan apply - wait 15 sec # networkctl reload - wait 15 sec # networkctl renew enP53p0s0.171 - wait 15 sec # networkctl reconfigure enP53p0s0.171 - wait 15 sec # networkctl reconfigure enP53p0s0.171 - wait 30 sec # networkctl status enP53p0s0.171 --no-pager # ip a === Findings from comment #33 (journalctl_udev_monitor.txt) === You executed "netplan apply" between 08:10:29 - 08:10:59 and it looks like systemd-networkd found the correct netplan-*.network configuration and applied it (assigned the IP) at 08:10:57. See "***" lines: Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Link state is up-to-date *** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: found matching network '/run/systemd/network/10-netplan-enP53p0s0.171.network' Jun 15 08:10:57 systemd-networkd[182847]: Setting '/proc/sys/net/ipv6/conf/enP53p0s0.171/disable_ipv6' to '0' Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: IPv6 successfully enabled Jun 15 08:10:57 systemd-networkd[182847]: Setting '/proc/sys/net/ipv6/conf/enP53p0s0.171/proxy_ndp' to '0' Jun 15 08:10:57 systemd-networkd[182847]: Setting '/proc/sys/net/ipv6/conf/enP53p0s0.171/use_tempaddr' to '0' Jun 15 08:10:57 systemd-networkd[182847]: Setting '/proc/sys/net/ipv6/conf/enP53p0s0.171/accept_ra' to '0' Jun 15 08:10:57 systemd-networkd[182847]: LLDP: Started LLDP client Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Started LLDP. Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Setting address genmode for link [...] *** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering updated address: 192.168.171.53/24 (valid forever) Jun 15 08:10:57 systemd-networkd[182847]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_37 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=45 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: dst: 192.168.171.53/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: host, table: local, proto: kernel, type: local Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: dst: 192.168.171.255/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link, table: local, proto: kernel, type: broadcast Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: dst: 192.168.171.0/24, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link, table: main, proto: kernel, type: unicast Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: dst: 192.168.171.0/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link, table: local, proto: kernel, type: broadcast *** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Addresses set *** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: State changed: configuring -> configured [...] Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: Processing device (SEQNUM=87120, ACTION=change) Jun 15 08:11:28 systemd-udevd[182940]: enP50s3832: /usr/lib/udev/rules.d/75-net-description.rules:12 Importing properties from results of builtin command 'hwdb --subsystem=pci' Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: /usr/lib/udev/rules.d/75-net-description.rules:6 Importing properties from results of builtin command 'net_id' Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: /usr/lib/udev/rules.d/80-net-setup-link.rules:5 Importing properties from results of builtin command 'path_id' Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: /usr/lib/udev/rules.d/80-net-setup-link.rules:5 Failed to run builtin 'path_id': No such file or directory Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: /usr/lib/udev/rules.d/80-net-setup-link.rules:9 Importing properties from results of builtin command 'net_setup_link' Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: Config file /etc/systemd/network/10-enP53p0s0.link is applied Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: Skipping to apply .link settings on 'change' uevent. Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: /usr/lib/udev/rules.d/80-net-setup-link.rules:11 NAME 'enP53p0s0.171' Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: sd-device: Created db file '/run/udev/data/n7' for '/devices/virtual/net/enP53p0s0.171' Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: Device (SEQNUM=87120, ACTION=change) processed When you try to manually assign the IP address afterwards, using the "ip" command it returns error "RTNETLINK answers: File exists", i.e. IP address is already assigned! That confirms that systemd-networkd apparently already successfully assigned the IP, as shown by the logs. => Could you please execute the same steps again, but wait some 30 sec after "netplan apply" and then execute "networkctl" and "ip a", to see if the IP is indeed assigned already? I.e.: # networkctl status enP53p0s0.171 --no-pager # ip a === Findings from comment #30 (journalctl_udevadm_netplan_ip.txt) === Between 08:12:02 - 08:12:12 you executed "netplan apply". => "link pending udev initialization..." Between 08:12:28 - 08:12:36 you executed "udevadm trigger". => A bit later, at 08:12:38 the magic happens: enP53p0s0.171: udev initialized link enP53p0s0.171: found matching network '/run/systemd/network/10-netplan-enP53p0s0.171.network' enP53p0s0.171: Setting address genmode for link enP53p0s0.171: State changed: pending -> configuring enP53p0s0.171: Remembering updated address: 192.168.171.53/24 (valid forever) enP53p0s0.171: Addresses set enP53p0s0.171: State changed: configuring -> configured Between 08:13:02 - 08:13:07 you execute "ip addr add ..." => RTNETLINK answers: File exists (I.e. IP address already assigned!) Could you execute the same steps again, but give some more time after "udevadm trigger" (like some 30 sec) and check "networkctl" and "ip a" afterwards? It looks like the IP was successfully assigned by systemd- networkd after all, but it took a while (for whatever reason). Jun 14 08:12:10 systemd-networkd[4102292]: enP53p0s0.171: New device has no master, continuing without Jun 14 08:12:10 systemd-networkd[4102292]: enP53p0s0.171: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST Jun 14 08:12:10 systemd-networkd[4102292]: enP53p0s0.171: Link 7 added *** Jun 14 08:12:10 systemd-networkd[4102292]: enP53p0s0.171: link pending udev initialization... Jun 14 08:12:10 systemd-networkd[4102292]: enP53p0s0.171: netdev has index 7 Jun 14 08:12:10 systemd-networkd[4102292]: enP53p0s0.171: Saved original MTU: 9000 [...] *** Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: udev initialized link Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Link state is up-to-date *** Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: found matching network '/run/systemd/network/10-netplan-enP53p0s0.171.network' Jun 14 08:12:38 systemd-networkd[4102292]: Setting '/proc/sys/net/ipv6/conf/enP53p0s0.171/disable_ipv6' to '0' Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: IPv6 successfully enabled Jun 14 08:12:38 systemd-networkd[4102292]: Setting '/proc/sys/net/ipv6/conf/enP53p0s0.171/proxy_ndp' to '0' Jun 14 08:12:38 systemd-networkd[4102292]: Setting '/proc/sys/net/ipv6/conf/enP53p0s0.171/use_tempaddr' to '0' Jun 14 08:12:38 systemd-networkd[4102292]: Setting '/proc/sys/net/ipv6/conf/enP53p0s0.171/accept_ra' to '0' Jun 14 08:12:38 systemd-networkd[4102292]: LLDP: Started LLDP client Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Started LLDP. *** Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Setting address genmode for link Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Setting address genmode done. Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Discovering IPv6 routers Jun 14 08:12:38 systemd-networkd[4102292]: NDISC: Started IPv6 Router Solicitation client *** Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: State changed: pending -> configuring Jun 14 08:12:38 systemd-networkd[4102292]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_37 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=49 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Setting addresses *** Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Remembering updated address: 192.168.171.53/24 (valid forever) Jun 14 08:12:38 systemd-networkd[4102292]: Sent message type=signal sender=n/a destination=n/a path=/org/freedesktop/network1/link/_37 interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=50 reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Remembering route: dst: 192.168.171.53/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: host, table: local, proto: kernel, type: local Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Remembering route: dst: 192.168.171.255/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link, table: local, proto: kernel, type: broadcast Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Remembering route: dst: 192.168.171.0/24, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link, table: main, proto: kernel, type: unicast Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Remembering route: dst: 192.168.171.0/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link, table: local, proto: kernel, type: broadcast *** Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: Addresses set *** Jun 14 08:12:38 systemd-networkd[4102292]: enP53p0s0.171: State changed: configuring -> configured -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929657 Title: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
