Hi Stefan, the network configuration and the setting of the IP addresses is triggered by netplan and done via systemd-networkd.
Nowadays no explicit renderer is needed anymore, in case there is none, networkd is used as default. (These days you only need to explicitly specify a renderer if you want to use a different one, which is possible but not supported.) One may add the "renderer: networkd" key, but I doubt that it will change anything. The requirement of the "version: 2" key is just that it needs to be on the same level (indention) like ethernets and vlan - which is the case. Positions should not make a difference (as long as it's under the correct key). Moving the enP53p0s0.171 should of course not change anything, too - but it's worth a try (since quickly done), just to ensure that there is no issue with the parsing or so. (One may re-write/re-type this entry on the top, just to make sure that no unusual characters are in - what I do not see, though ...) Another try would be to test not setting an IP to the base device, so just on the vlan interface only. Btw. Stefan, what do you think about this 'unusual' name "enP50s3832" of the other RoCE device? Interestingly this is the one where things work ... (I saw plans about introducing more predictable names for RoCE interfaces ...) -- 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
