So I tried to recreate and provoke any problems with the IP addresses on a test LPAR that has in between 5 OSA based qeth devices (4 of them with two addresses - one on base, one on the vlan device) and 4 RoCE (v1) ports. Other than finding out that one of the RoCE ports has probably no link (which is a different issue) everything worked fine so far.
And the journal log you provided (thx for that) only shows that the enP53p0s0.171 is not activated (at least for ipv6) after the second systemd network-service start: ... Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd[1]: Starting Network Service... Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdb0.160: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdc0.150: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP50s3832.170: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP53p0s0.171: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP53p0s0: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP50s3832: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: ence0f: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdc0: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdb0: Gained IPv6LL Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: Enumeration completed Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd[1]: Started Network Service. Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdb0.160: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdc0.150: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP50s3832.170: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP53p0s0: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: enP50s3832: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: ence0f: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdc0: IPv6 successfully enabled Jun 07 13:04:05 ilabg13.tuc.stglabs.ibm.com systemd-networkd[2097602]: encdb0: IPv6 successfully enabled ... On the first the seems to be some activity. Unfortunately there are not enough details (in the regular journal log) to dig deeper into this - the above snippet is largely it. Would it be possible to enable verbose journaling 'journalctl -o verbose' hoping that we are then able to find more details - not sure what it will bring on top (or if this is not sufficient maybe even running systemd in debug mode). -- 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
