During installation with Subiquity, can't connect to network and install halts

[Marc Erickson]

Installing Ubuntu 18.04.2 Server on a Dell T310 PowerEdge server with two built in network connections. The installer says there isn't a response from the DHCP server (my home router) on either interface. I tried configuring eth0 manually: Netmask - 192.168.1.0/24 Static IP - 192.168.1.252 DNS - 8.8.8.8, 8.8.4.4 Search domain - google.com.

Saving these settings causes the installer to go back a few steps to "Select language".

After trying everything I could think of - connecting both NICs to the network (installer again reports no response from DHCP server), configuring eth1 first, bonding the two NICs together and then configuring them, disabling the two NICs in the UEFI (on this box someone can't disable only one - it's all or nothing) (I might have tried one or two other things but can't remember them now), I gave up.

Also reported here:
https://serverfault.com/questions/967461/ubuntu-install-restarts-every-time-a-manual-network-connection-is-configured
https://askubuntu.com/questions/1124742/ubuntu-18-04-2-lts-server-network-configuration-problem-during-setup

[Marc Erickson (marcerickson)]

"Saving these settings" should read "Trying to save these settings"

[Michael Hudson-Doyle (mwhudson)]

Can you try the 19.04 installer? We made some changes here which will be included in the 18.04.3 release but it would be good to know if they help before that gets released!

[Marc Erickson (marcerickson)]

I tried Server 1904 from the installation image ubuntu-19.04-live-server-amd64.iso on the same PowerEdge T310. Both NICs were connected to the network. Again, Setup reported that DHCP did not respond. I was able to configure eth0 manually. When done, the selection at the bottom said "Continue without network" or "Back". I chose "Continue without network". Installation concluded normally. After rebooting, computer was able to access the internet and install programs and updates.

This testing was done on a hard drive I installed temporarily. I've now returned to using the original 18.0.2 boot drive in that server so that I can continue curating my music collection. ;-)

[Marc Erickson (marcerickson)]

Of course I meant Server 19.04.

[ovingiv (ovingiv)]

I'm also having the same issue. From what I could gather, the eth0 and eth1 are named eno1 and eno2.

[Michael Hudson-Doyle (mwhudson)]

I think this is fixed now, please reopen if you disagree.

[Marc Erickson (marcerickson)]

Seems to be fixed. Test installed Ubuntu Server from the ubuntu-19.04-live-server-amd64.iso I downloaded a few days ago. Installer 19.04.4 tested and installed OK. I then tried the 19.11.1 installer. It installed successfully. Both failed to boot after the installation - they failed at "Reached target cloud-init target" - but that is beyond the scope of this ticket.

[Michael Hudson-Doyle (mwhudson)]

I'm glad this bug is fixed, installing non-booting systems is certainly not
good though! Can you file a bug about that?

[ovingiv (ovingiv)]

I'm still having this issue when post installed trying to download updates.

[ovingiv (ovingiv)]

I installed 18.04.3-live.iso and also had the same issue when pre-installed where it timed out trying to get network info from DHCP.