Subiquity DHCP bug

[mtsec]

Ubuntu Server 18.04.2 LTS

There appears to be a bug in subiquity regarding the automatic configuration of the network parameters via DHCP.

As the screenshots show, during the installation of Ubuntu Server 18.04.1 LTS, an IP address is assigned to the server via DHCP. When running the Ubuntu Server 18.04.2 LTS installer on the same server (see the trailing end of the MAC addresses) with the same (default) settings, no IP address is assigned during the network setup.

As this bug appeared in Ubuntu Server 18.04.2 LTS, while it is not present in Ubuntu Server 18.04.1 LTS, it seems to be a regression bug in subiquity.

Information about the NIC in question can be found here: https://h20195.www2.hpe.com/v2/getpdf.aspx/c04111370.pdf

[Michael Hudson-Doyle (mwhudson)]

That's strange, the dhcp part is all handled by systemd-networkd really so I don't think any subiquity changes here are very relevant. Is there anything revealing in the journal or syslog?

[mtsec (j-mint)]

Not as far as I could see during the normal installation flow. As I can easily reproduce this issue, which logs would you like to receive? Please include instructions on how to escape to the terminal from within subiquity and the location of the logs you're interested in.

[Michael Hudson-Doyle (mwhudson)]

You can escape to the terminal by switching to another vt with ctrl-alt-f2 or similar. The files I'd be interested in are /var/log/syslog or the output of "sudo journalctl". Of course getting the files off the server might be fun if the network isn't getting set up, I guess you'll need to plug another USB drive in or something?