Bug 2419063

Summary: blivet-gui creates partition (RAID device?) smaller than requested
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: blivet-guiAssignee: Vojtech Trefny <vtrefny>
Status: ASSIGNED --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: mkolman, vtrefny
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
storage.log from an affected install none

Description Adam Williamson 2025-12-05 01:18:33 UTC 
In https://openqa.fedoraproject.org/tests/4037123 , at https://openqa.fedoraproject.org/tests/4037123#step/disk_custom_blivet_software_raid/31 , you can see that openQA requests a /boot partition of size 1024 MiB. But at https://openqa.fedoraproject.org/tests/4037123#step/disk_custom_blivet_software_raid/33 you can see that it actually gets created at a size of 1023 MiB.

This later causes the test to fail because anaconda shows a warning bar that it's not expecting. The warning (from storage.log) is:

DEBUG:anaconda.modules.storage.partitioning.validate:Found sanity warning: Your /boot partition is less than 1024 MiB which is lower than recommended for a normal Fedora install.

so...we asked for a 1024 MiB /boot, anaconda gave us a 1023 MiB /boot, then lectured us about it. That's not great user experience!
Comment 1 Adam Williamson 2025-12-05 01:19:36 UTC 
Looks like this might be specific to RAID. I'll attach the log files.
Comment 2 Adam Williamson 2025-12-05 01:20:21 UTC 
Created attachment 2117464 [details]
storage.log from an affected install
Comment 3 Vojtech Trefny 2025-12-09 11:26:16 UTC 
Unfortunately the size selection here doesn't take the RAID metadata size into account (or any metadata at all in general, for encrypted RAID, the resulting array size would be even smaller) so the two 1024 MiB RAID partitions will produce only 1023 MiB RAID 1 array. I agree this is not a good user experience and I'll try to find a way how to display this in a better way and include the metadata size.