This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2175911 - Unable to allocate requested partition scheme
Summary: Unable to allocate requested partition scheme
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: python-blivet
Version: 8.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Blivet Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 2129764
TreeView+ depends on / blocked
 
Reported: 2023-03-06 18:40 UTC by Jiri Kortus
Modified: 2023-09-23 12:35 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-23 12:35:40 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-8026 0 None Migrated None 2023-09-23 12:35:34 UTC
Red Hat Issue Tracker RHELPLAN-150858 0 None None None 2023-03-06 18:46:22 UTC

Description Jiri Kortus 2023-03-06 18:40:33 UTC 
Description of problem:
The following change to physical partition location in an automatically created partitioning in Anaconda failed on me: I used a machine with 1 GiB disk (vda) and 10 GiB disk (vdb), selected manual partitioning and clicked on the 'link' to create the partitioning automatically. Then I chose /boot partition and modified its physical location to only use vda. When I wanted to do a subsequent step, i. e. shrink / partition and modify the related LV to only reside on the other disk (vdb), the whole partitioning disappeared and the error message bar on the bottom of the screen appeared, with its details stating 'Unable to allocate requested partition scheme'

Version-Release number of selected component (if applicable):
python3-blivet-3.6.0-4.el8, anaconda-33.16.8.8-1.el8 (RHEL-8.8.0-20230228.22)

How reproducible:
100%

Steps to Reproduce:
1. Prepare a VM with two disks, #1 - 1 GiB, #2 - 10 GiB
2. Start system installation, advance to partitioning spoke and select manual partitioning.
3. On the manual partitioning screen, click on 'Click here to create them automatically'.
4. Select /boot partition and modify it to be located only on disk #1.
5. Click on / partition.

Actual results:
The existing partitioning gets removed and error bar appears on the bottom of the screen, saying 'Unable to allocate requested partition scheme' when you click on it to see details.

Expected results:
It's possible to do further steps after step 4., i. e. shrink / partition and change the related LV to be only located on disk #2 (and likely also shrink /boot a bit as it wouldn't fit a 1024 MiB disk). The error is only displayed when user tries to exit the spoke with an invalid partitioning.

Additional info:
The same issue also happens when I just tried to shrink the /boot partition, without touching where it should be located physically. I wasn't able to finish the partitioning by modifying the automatically created one. The only way that worked for me with this particular two-disk configuration was to use a manual partitioning and create /boot first, change its physical location, and the create swap and /.
Comment 7 RHEL Program Management 2023-09-23 12:34:45 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 8 RHEL Program Management 2023-09-23 12:35:40 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.