Hi Mario, thanks for coming back to this case. So it seems that the situation is now good again - now that the /etc/systemd/network/10-enP53p0s0.link got removed.
We don't know a tool or application offhand that would create such a .link file in /etc/systemd/network/ alone. However, there are plenty of tools that generate files in this context, like netplan, udev, NetworkManager, etc. - but then such automatically created files would be usually located at /run/systemd/network - /etc is more for manually created ones. Maybe this was caused by a less common tool that does not stick to this (de-facto) standard. Or maybe it got copied there by accident, while backing up files or so - difficult to say. We at least don't imagine a case where such a file is created by the standard Ubuntu tooling. You didn't had a chance to grab the stats for that file before having removed it, did you? Do you agree that the bug can be closed now based on finding the cause (the .link) file, having it removed and now the system behaving as expected again? -- 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
