subiquity

Ubuntu 20.04-Nimble boot from SAN install system crash

Bug #1890651 reported by Eddie Campbell
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
New
Undecided
Unassigned

Bug Description

While performing boot from SAN install of Ubuntu20.04 on a Nimble Volume, the system crashes at the install screen where we configure Ubuntu archive mirror after we choose the default value and select Done.

Steps for repro:

1) Create a Nimble volume and map it to the HBA on the server.
2) Start the installation process.
3) When we get to the screen to configure Ubuntu archive mirror, choose default values and select “Done”

Result -> The system crashes with the message generating crash dump ( see attached screen shot ).

Additional details:

 This issue has been seen with both QLogic and Emulex HBA’s
 This issue has been seen on both HP Proliant servers as well as Fujitsu servers
 Boot from San install of Ubuntu 18.04 works on Nimble Volumes.
 I was able to successfully install Ubuntu 20.04 on local hard drive that makes me think this has something to do with Ubuntu interaction with Nimble volumes.

I was able to successfully install using the legacy installer. I didn't hit the issue seen using the live-server installer.

Revision history for this message
Eddie Campbell (eddie-campbell) wrote :
Revision history for this message
Michael Reed (mreed8855) wrote :

I requested an install using the legacy installer

http://cdimage.ubuntu.com/ubuntu-legacy-server/releases/20.04/release/ubuntu-20.04-legacy-server-amd64.iso

As it states in the description, they were able to successfully install using the legacy installer.

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

Hmm that's strange. Can you try the recently released 20.04.1 installer? Can you provide the crash file that should be generated in /var/crash in the live session?

Revision history for this message
Amaresh Thamizhakaran (amaresht) wrote :

I tried with the ubuntu-20.04.1-live-server-amd64 installer and still hit the same issue. I am attaching the crash file.

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

Ah the installer is getting confused because disks sdc-sdj (the paths to the SAN it seems) show up as multipath members but do not have a wwn in udev -- is that expected? They do seem to have a wwn in the 'multipathd show paths' output.

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

It's easy to fix the immediate cause of the crash but I'm not sure if this lack of wwn in the storage config will cause problems later. One way to find out I guess!

Revision history for this message
Amaresh Thamizhakaran (amaresht) wrote :

Since the issue is not seen with the legacy installer, is it possible to handle this scenario the same way as in legacy installer on the live-server installer?

Revision history for this message
Andrew Cloke (andrew-cloke) wrote :

@Michael, it would sound like the best next step is to address the immediate cause of the crash and see how the installation proceeds from there. Would that be relatively simple to achieve?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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