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.

Description of problem:
When bootloader doesn't have --boot-drive parameter then a first disk from Blivet is used. It looks like Blivet is sorting the disk alphanumerically so the bootloader is written to 'sda' or 'vda' and similar. 
Boot drive should be taken from --driveorder and if --driveorder is not present then take disk where /boot is. If nothing can be used, take first from Blivet.

Version-Release number of selected component (if applicable):
anaconda-25.20-1

How reproducible:
Always

Steps to Reproduce:
1. Create KS with bootloader "bootloader --location=mbr" (or specify --driveorder) and with /boot on disk /dev/sdb or /dev/vdb  and other required stuff for auto-install
2. Start fully automatic installation with KS
3. After the installation, look to the program log to see if grub2-install is used on the disk where /boot is (or first disk in --driveorder field if specified)

Actual results:
Without the --boot-drive the bootloader is installed to first disk

Expected results:
The bootloader should be installed to a first disk from --driverorder field or /boot if driveorder isn't specified.

PR: https://github.com/rhinstaller/anaconda/pull/700

PR: https://github.com/rhinstaller/anaconda/pull/706

Reproduced on RHEL-7.2, verified on RHEL-7.3-20160901.1 with anaconda-21.48.22.86-1.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2158.html