I confirm I got it working at first boot on azure with
systemd-245.4-4ubuntu3.4
```
ubuntu@machine-3:~$ sudo networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eth0 etherroutableconfigured
2 links listed.
ubuntu@machine-3:~$ sudo apt update
Sadly, the journalctl logs don't go back that far now.
It failed on a baremetal server, not a cloud.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1904549
Title:
MTU is
Hello,
I don't need it on bond-manlan for sure (MTU 1500 on this one and its VLANs),
but I read in several place that setting MTU on the bond would also set it on
interface members.
And that indeed worked correctly.
As I said, I think the issue is definitely more in the udevd/networkd
part
Thanks for the explanation.
I confirm that the workaround using "sytemctl restart systemd-udev-
trigger && systemctl restart systemd-networkd" does the trick.
@Dan Watkins : did you do some specific thing to reproduce the issue on
your local VM ? It would be interesting to see the whole logs
Here is a pastebin of the situation and how I tried to resolve this :
https://pastebin.ubuntu.com/p/c6cfKqvBmN/
Unfortunately, the interface stays "unmanaged".
When I check the netplan source
(https://github.com/CanonicalLtd/netplan/blob/master/netplan/cli/commands/apply.py#L128),
it just stops
5 matches
Mail list logo