subiquity

Installer crashes during install if VROC RAID is undergoing initialization.

Bug #1939563 reported by Mateusz Kusiak
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
curtin
Fix Released
Undecided
Unassigned
subiquity
Fix Released
Undecided
Unassigned

Bug Description

Installer crashes during VROC RAID initialization. Waiting for the initialization to end will allow to properly complete installation.

Steps to reproduce:
1. Enable VMD on slot corresponding to SSDs user plans to use in RAID;
2. Configure RAID 5;
3. Reboot and boot to Ubuntu server live installation;
4. In case of pre-release 21.04.2 + update configuration, switch to second console (ALT+F2), and ensure that network is configured, and update subiquity:
snap refresh --edge subiquity
After download it should restart the installer automatically;
5. Continue install as normal.

Behaviour:
Installer crashes shortly after selecting installation destination to RAID, before copying data.
It happens only during initialization. After the innitialization is complete, installer works properly without a crash.

Version: Subiquity pre-release public beta

Tags: vroc

Related branches

~mwhudson/curtin:install-to-resyncing-raid
Server Team CI bot: Approve (continuous-integration)
Dan Bungert: Approve
Diff: 16 lines (+3/-2)
1 file modified
curtin/block/mdadm.py (+3/-2)
Revision history for this message
Dan Bungert (dbungert) wrote :

Thanks for that.
Would you be able to share the /var/log/installer/subiquity-server-debug.log.<pid> file? There will probably a few based on your steps above, the biggest one should be fine.

Changed in subiquity:
status: New → Incomplete
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

yes, curtin only wants to install to arrays that are 'idle', not any other sync_action. I don't know why, exactly -- installing to an array while it is reshaping or something would be pretty strange but I don't know that we should try to prevent it, and installing while syncing seems definitely ok.

Revision history for this message
Server Team CI bot (server-team-bot) wrote :

This bug is fixed with commit cf07c230 to curtin on branch master.
To view that commit see the following URL:
https://git.launchpad.net/curtin/commit/?id=cf07c230

Changed in curtin:
status: New → Fix Committed
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

Hi Mateusz, we included a tentative fix for this in the 21.08.1 release so if you're able to re-test that (using a focal or impish daily, or by using whichever ISO you were using before and taking the offered update), that would be great.

Revision history for this message
Mateusz Grzonka (mgrzonka) wrote :

Hi Michael,
we tested the fix for this using the ISO 20.04.2 LTS, as before.
subiquity 21.08.1+git15.1c06aba1 (ver. 2640) was used.
During testing we got an update to subiquity 21.08.1+git17.1001cdc9 (2655), see below.
Installation went successfully for (we also tested other RAIDs, just to be sure):
* RAID10,
* RAID5, -> here we got an update (see step 4)
* RAID5 with PPL,
* matrix (RAID5+RAID10),
* matrix (RAID5+RAID10) with LVM.

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

Thanks for reporting back. 20.04.3 will go out in about 24 hours so I'm glad to hear beforehand that things work!

Michael Hudson-Doyle (mwhudson)
Changed in subiquity:
status: Incomplete → Fix Released
Revision history for this message
Dan Bungert (dbungert) wrote : Fixed in curtin version 21.3.

This bug is believed to be fixed in curtin in version 21.3. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in curtin:
status: Fix Committed → Fix Released
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.