network screen fails to show IP when netbooted

Bug #1914469 reported by dann frazier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
New
Undecided
Unassigned
busybox (Ubuntu)
New
Undecided
Unassigned

Bug Description

focal 20210201.2 installer on z Cavium ThunderX CRB2S system (hostname recht)

Even though the network was automatically configured successfully via DHCP, the "Network connections" screen shows only "-" in the NOTES section. I believe on other platforms it usually shows the IP address. I've booted the installer twice, and it has occurred both times.

The install proceeds to completion successfully, it is just non-obvious that the network has in fact successfully configured at this point in the install.

Tags: iso-testing
Revision history for this message
dann frazier (dannf) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1914469

tags: added: iso-testing
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Hmm. Can you attach /var/log/installer/subiquity-server-debug.log?

Revision history for this message
dann frazier (dannf) wrote :
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Sorry for the slow response. So the reason the addresses aren't showing up in the UI is that they are "permanent" in the sense of IFA_F_PERMANENT which is not what the code expects for an address received via DHCP. What component is actually doing the DHCPing? Is it or the installer wrong? :)

Revision history for this message
dann frazier (dannf) wrote :

The installer is doing the DHCP'ing, there's nothing strange going on there. I do know that this platform has a non-conventional networking architecture - maybe there's some mismatched assumptions there.

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Hm strange. Can you attach the journal? Not sure how verbose networkd is by default, if there's anything you know of to make it more verbose, please do that too :)

Revision history for this message
dann frazier (dannf) wrote :

I netbooted, created an /etc/systemd/system/systemd-networkd.service.d/10-debug.conf:
[Service]
Environment=SYSTEMD_LOG_LEVEL=debug

restarting systemd-networkd and captured the attached journal.

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

For some reason this bug always falls away from my attention, sorry.

If you netboot it's not networkd assigning the addresses? I'm not sure where the output from the initramfs ends up but it's not in the journal, can you reproduce and attach dmesg maybe?

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

There is one thing odd in the logs though:

Apr 09 18:48:03 ubuntu-server systemd-networkd[3059]: enP2p1s0v0: Remembering foreign address: 10.229.66.189/16 (valid forever)

It's strange for a dhcp allocated address to be valid forever. Unfortunately networkd doesn't log the address flags in this situation.

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Oh wait, this seems to happen for all netboots (at least currently) :( I think it's because of the think I mentioned in comment #10: the busybox ip command does not support the valid_lft flag, and the kernel sets the IFA_F_PERMANENT flag on any address without a lifetime, and then subiquity assumes it was manually assigned vs arriving via DHCP.

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Oh heh looks like this is fixed in busybox upstream! https://git.busybox.net/busybox/commit/?id=8a485b0a363935309f976866b8a30988362fadc0

Not sure when that will make it's way into Ubuntu though.

dann frazier (dannf)
summary: - network screen fails to show IP on crb2s system
+ network screen fails to show IP when netbooted
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.