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 985163 - Install does not allow bootloader configuration
Summary: Install does not allow bootloader configuration
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-17 01:37 UTC by Alex Williamson
Modified: 2013-12-11 16:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-11 16:29:01 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Alex Williamson 2013-07-17 01:37:34 UTC 
Description of problem:
I boot multiple installations from a single disk.  RHEL5 allows configuration of where the bootloader is installed (MBR vs partition).  RHEL6 allows configuration of where the bootloader is installed.  RHEL7 don't care, RHEL7 overwrites the MBR.

Version-Release number of selected component (if applicable):
RHEL7 pre-beta

How reproducible:
100%

Steps to Reproduce:
1. Attempt to install RHEL7 and finish with the MBR intact
2.
3.

Actual results:
RHEL7 now owns the MBR

Expected results:
No regression from RHEL5 and RHEL6 which allow partition installation.

Additional info:
Comment 2 David Cantrell 2013-12-11 16:29:01 UTC 
The RHEL-7 installer allows you to select the whole disk that you want the boot loader installed on.  You can also choose to not install a boot loader.  The link in the lower left corner of the INSTALLATION DESTINATION screen called "Full disk summary and bootloader..." allows you to pick an alternate disk or not install a boot loader at all.

More advanced boot loader configuration settings are available via kickstart.
Note You need to log in before you can comment on or make changes to this bug.