Hi all,
I didn't see a response to the workaround, so just dropping a message.
I had the same issue. Confirming that workaround - configuring my
`/etc/netplan/50-cloud-init.yaml` to match the network interface based
on macaddress (`ip a`), and applying the change (`netplan generate &&
netplan
Hi Lucas,
In your scenario the best approach would probably be relying on Netplan
to rename the interface for you instead of creating an external udev
rule.
I'd suggest you use "set-name: eno1" and continue to use "match" in your
configuration. Something like this:
```
network:
version: 2
** Tags added: foundations-todo network-online-ordering
** Changed in: netplan.io (Ubuntu)
Status: New => Triaged
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I think I understood this.
I have a udev rule to force the NIC name to eno1, which is not the
driver's default (it is eno1np0). I did not regenerate the initramfs, so
that rule did not propagate there.
What happens is:
- initramfs is executed. The NIC is renamed to eno1np0 (driver's default).
-
It worked fine in Ubuntu 23.10: network-online.target is only reached
after eno1 is configured.
# journalctl -b |grep -e network -e grid5000.mount
Apr 28 00:23:06 localhost kernel: drop_monitor: Initializing network drop
monitor service
Apr 28 00:23:06 localhost systemd[1]: Listening on
