subiquity creates wrong network configuration (wrong NIC name)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I already reported a bug against other tool but I think it should be filled against subiquity.
https:/
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/
#####
# 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/
It looks like your nic changed name after the reboot. I don't know why that would happen.