Description of problem: In Anaconda webUI storage configuration, when I want to create a 1 MB biosboot partition, it creates a 999 MB partition instead. Version-Release number of selected component (if applicable): Fedora-Workstation-Live-x86_64-Rawhide-20240211.n.0.iso anaconda-40.21-2.fc40.x86_64 anaconda-core-40.21-2.fc40.x86_64 anaconda-gui-40.21-2.fc40.x86_64 anaconda-install-env-deps-40.21-2.fc40.x86_64 anaconda-live-40.21-2.fc40.noarch anaconda-tui-40.21-2.fc40.x86_64 anaconda-webui-5.2-1.fc40.noarch anaconda-widgets-40.21-2.fc40.x86_64 cockpit-bridge-310.2-1.fc40.x86_64 cockpit-storaged-310.2-1.fc40.noarch cockpit-system-310.2-1.fc40.noarch cockpit-ws-310.2-1.fc40.x86_64 How reproducible: always Steps to Reproduce: 1. run anaconda with a clean disk 2. go to storage configuration, create a new partition 3. select biosboot type, 1 MB size 4. see that 999 MB partition was created
Created attachment 2016461 [details] bug screencast
Created attachment 2016462 [details] anaconda.log
Created attachment 2016463 [details] program.log
Created attachment 2016464 [details] storage.log
Proposing as a F40 Beta blocker: "When using both the installer-native and the blivet-gui-based custom partitioning flow, the installer must be able to: Assign sizes to newly-created storage volumes and containers" https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria#Custom_partitioning
> In Anaconda webUI storage configuration, when I want to create a 1 MB biosboot partition, it creates a 999 MB partition instead. Yes, this is very likely fixed by https://github.com/cockpit-project/cockpit/pull/19929. Thanks!
Discussed during the 2024-02-12 blocker review meeting: [0] The decision to classify this bug as an "AcceptedBlocker (Beta)" was made as it violates the following criterion: "When using both the installer-native and the blivet-gui-based custom partitioning flow, the installer must be able to: Assign sizes to newly-created storage volumes and containers". Technically it can do that, but not in a way that makes any sense to a user. We are considering cockpit to be the 'installer-native' custom partitioning flow for current Workstation live images. [0] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-02-12/f40-blocker-review.2024-02-12-17.05.txt
There is one more wrinkle, unfortunately: Something in the storage stack causes a partition to be about 1 Mb smaller than requested. So trying to make a 1 MB partition ends up with a 512 byte partition... This needs fixing as well for biosboot partitions, but probably doesn't impact normal multi-GB partitions signifcantly.
(In reply to Marius Vollmer from comment #8) > There is one more wrinkle, unfortunately: Something in the storage stack > causes a partition to be about 1 Mb smaller than requested. Thanks, I reported that as bug 2264412.
In my testing, this seems resolved in Fedora-Workstation-Live-x86_64-40-20240216.n.0.iso.