> Gave some time between netplan apply and check without success, I can leave 
> it for
> hours and the IP never gets assigned

Indeed, I cannot see it being assigned an IPv4 address in your latest
"_delay" run. (Well, there is some assignment of an IP to enP53p0s0.171
at 15:05:29 in the journal logs, but that was before you started the
experiment).

> maybe what you are seeing is the manual assignment that I did with
> ip addr add 192.168.171.53/24 dev enP53p0s0.171

No I don't think so, as the timestamp of your manual "ip addr add"
command (08:13:02++) is after the systemd-networkd assignment in the
logs (08:12:38). Also, your output clearly shows that the IP was already
assigned when you tried to (re-)assign it manually (it shows the
"RTNETLINK answers: File exists" error):

> root@ilabg13:~# ip addr add 192.168.171.53/24 dev enP53p0s0.171
> RTNETLINK answers: File exists

I'm a bit worried about the /etc/systemd/network/10-enP53p0s0.link file (now 
there seems to be another one "10-enP53p0s0.link" as well...) – Is this file 
needed? Why was it created?
It matches on "MACAddress=82:0c:9b:c9:78:f8", which would match enP53p0s0 AND 
enP53p0s0.171 at the same time (they use the same inherited MAC address), 
leading to unspecified behavior, as we cannot rename two interfaces to the same 
"Name=enP53p0s0".

Could you try deleting this file in /etc/systemd/network/10-enP53p0s0.link 
(potentially adopting your netplan YAML config to the name assigned to this 
interface by the kernel/systemd) and check if this makes any difference?
# rm /etc/systemd/network/10-enP53p0s0.link

If for some reason you cannot delete this file, try adding a "Type=!vlan" line 
instead:
# cat /etc/systemd/network/10-enP53p0s0.link
[Match]
MACAddress=82:0c:9b:c9:78:f8
Type=!vlan

[Link]
Name=enP53p0s0

Does this make any difference when running "netplan apply && sleep 30 &&
networkctl status -a --no-pager"?

-- 
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

Reply via email to