*** This bug is a duplicate of bug 1882162 ***
https://bugs.launchpad.net/bugs/1882162
@slyon - I use unraid here, and if I modify the VM configuration at all
(I just mounted an unraid share through unraid's VM manager, and
rebooted my Ubuntu Server - no IP address). I made no changes beyond
that, which seems odd, (and I understand that unraid's VM manager is not
applicable per-say here) just figured I would provide the additional
information. Seems to happen anytime the configuration changes - the
device name in Ubuntu is modified, but the netplan configuration keeps
the original ethernet device name from the install. In this specific
case, 00-installer-config.yaml has the device name as enp1s0, but the
correct device name is now enp3s0. Luckily, I know how to fix, but its
quite impactful.
IMHO, the issue is the installer's eth device path, which clearly
changes later on in the lifecycle of the VM but netplan doesn't
recognise nor modify it's config.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881832
Title:
Ubuntu server 20.04 fails to get IP address from DHCP server (no
network connectivity)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1881832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
