Description of problem: When adding a 1MB biosboot partition, I get an error "Unable to allocate requested partition scheme". Version-Release number of selected component (if applicable): anaconda-21.48.6-1.fc21.x86_64 How reproducible: Always with this particular configuration, uncertain of scope. Steps to Reproduce: 1. Manual Partitioning, add / partition without specifying size. 2. Click Done. 3. I get a message indicating a BIOSBoot partition is required. 4. Add Biosboot partition 1MB Actual results: Red banner appears at the bottom of the page, clicking on it reveals "Unable to allocate requested partition scheme". UI shows 2014.5KiB available space so that shouldn't be the problem Expected results: Best: Add the required BIOSBoot partition for me without asking. Minimum: Honor this manual request without error. Additional info:
Created attachment 938188 [details] screenshot
Created attachment 938189 [details] anaconda.log
Created attachment 938190 [details] program.log
Created attachment 938191 [details] storage.log
Starting from the above failure: 5. Reset selections 6. Add new mount point biosboot 1mb Same problem, "Unable to allocate requested partition scheme" python-blivet-0.62-1.fc21
Proposed as a Blocker for 21-beta by Fedora user chrismurphy using the blocker tracking app because: When using the custom partitioning flow, the installer must be able to Create mount points backed by ... Biosboot is not in the criteria list, but it's required for BIOS+GPT installations, so it stands to reason the installer must be able to create biosboot in the custom partitioning flow (either automagically behind the scenes, or per user request)
It does seem related to space, yet the error message doesn't even remotely indicate this. If I create biosboot first it works. If I specify a capacity for /, and then create biosboot, then it works. Only if I create / first (as LVM or Standard partitioning) without specifying capacity, then creating a 1mb biosboot fails.
so I think the behaviour overall is as designed, but I see a couple of issues: 1. anaconda showing 'free space' it can't actually use (we'd need more details on the disk layout to diagnose that, I guess) 2. The misleading error message
Discussed in 2014-09-24 Blocker Review meeting [1]. Rejected as a blocker. This bug doesn't really violate any criteria but would be good to fix the display of free space. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2014-09-24/
*** This bug has been marked as a duplicate of bug 1162202 ***