Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1022643

Summary: requires user manually create biosboot when using guided partitioning
Product: Red Hat Enterprise Linux 7 Reporter: Brian Lane <bcl>
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.0CC: amulhern, anaconda-maint-list, bcl, bugzilla, dlehman, dshea, g.kaviyarasu, jonathan, mkolman, mruckman, robatino, sbueno, vanmeeuwen+fedora
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1021258 Environment:
Last Closed: 2013-10-23 23:00:52 UTC 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:
Bug Depends On: 1021258    
Bug Blocks: 980651    

Description Brian Lane 2013-10-23 17:11:27 UTC
+++ This bug was initially created as a clone of Bug #1021258 +++

Description of problem: When installing using Guided partitioning path to a GPT disk containing 2 or more partitions, and at least one of them will be preserved, the installer refuses to proceed telling the user a biosboot partition is required.


Version-Release number of selected component (if applicable):
F20 beta TC5
anaconda-20.25.1-1
python-blivet-0.23.1-1

How reproducible:
Always

Steps to Reproduce:
1. Existing GPT disk with 2+ partitions that are not a BIOS boot partition.
2. Guided partitioning, Installation Options: "I want more space"; continue
3. In Reclaim Disk Space, delete one or more partitions, preserving at least one; click Reclaim Space button.

Actual results:
Error, requires user to use Manual Partitioning to create a biosboot partition.

Expected results:
To create the required partition for me.

Additional info:

--- Additional comment from Brian C. Lane on 2013-10-22 20:25:54 EDT ---

Could you give this a try (against TC5)?

http://bcl.fedorapeople.org/updates/1021258.img

It moves the bootloader execute back the way it was.

It also fixes reusing an existing /boot/efi in autopart.

--- Additional comment from Chris Murphy on 2013-10-22 22:21:34 EDT ---

(In reply to Brian C. Lane from comment #9)
> Could you give this a try (against TC5)?
> http://bcl.fedorapeople.org/updates/1021258.img

Fixes this bug.

Comment 2 Brian Lane 2013-10-23 23:00:52 UTC
This is actually fixed by the patch for bug 1022418

*** This bug has been marked as a duplicate of bug 1022418 ***