Public bug reported:

I already reported a bug against other tool but I think it should be
filed agains subiquity.

https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1881832

Ubuntu server 20.04 and 18.04.4. When I installed them on virtual
machine (FreeNAS 11.3, VMware ESXi 6.7), installation was OK but after
reboot, virtual machine had no network connectivity, IP address from
DHCP server was not requested. NIC interface was enp0s4. I can ask for
IP address manualy with "sudo dhclient enp0s4" and it works!

I think that issue is that subiquity creates wrong network
configuration, this is file after install. Nnote, that enp0s5 is
configured with DHCP4, but real NIC is enp0s4...

/etc/netplan/00-installer-config.yaml

#####
# This is the network config written by 'subiquity'
network:
  ethernets:
    enp0s5:
      dhcp4: true
  version: 2

I fixed this issue by replacing "enp0s5" with "enp0s4" in file
/etc/netplan/00-installer-config.yaml. Rebooted machine asked for IP
address from DHCP server and I like it...

** Affects: subiquity (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882162

Title:
  subiquity creates wrong network configuration (wrong NIC name)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1882162/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to