Bug 2264517

Summary: WebUI: The installer doesn't suggest or check the order of partitions
Product: [Fedora] Fedora Reporter: Jan Stodola <jstodola>
Component: anaconda-webuiAssignee: Katerina Koukiou <kkoukiou>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: anaconda-maint, jkonecny, kkoukiou, mkolman, mvollmer, rvykydal, slavik.vladimir, w
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-02-21 10:24:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2231339    
Attachments:
Description Flags
webui.log none

Description Jan Stodola 2024-02-16 09:32:23 UTC 
I blindly followed the requirements in the Cockpit Storage screen in anaconda, which says:

=====================
Partitions (advanced)
If you are configuring partitions the following are required:
    /
    biosboot
Recommended partitions:
    /boot
======================

I created them in the same order:
1. /
2. biosboot
3. /boot

The installer allowed me to begin the installation, but the installation crashed later when installing the bootloader. This is expected, since the biosboot partition was not created as the first partition vda1, but as vda2.

The installer should tell the order the partitions should be created if it is necessary, like in the case of biosboot.

Also, the installer should not allow to begin the installation if the order of the partitions is not correct.

Reproducible: Always
Comment 1 Jan Stodola 2024-02-16 09:33:09 UTC 
Created attachment 2017171 [details]
webui.log
Comment 2 Marius Vollmer 2024-02-20 20:58:03 UTC 
From the logs: warning: Your BIOS Boot Partition is under 1 MiB, please increase its size..

I think it's not the position, but the size that is the problem.
Comment 3 Jan Stodola 2024-02-21 10:24:08 UTC 
You are right, Marius, I hit a problem reported in bug 2264412 and incorrectly assumed the problem was with the order of partitions.
I've retested the same scenario again, the partition order doesn't seem to matter and the biosboot partition doesn't have to be the first one. Also the GTK installer in RHEL-9 is fine when the biosboot partition is not the first one on the disk.

I'm sorry for the noise and I'm closing this bug.