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.
This bug was initially created as a copy of Bug #2054606
Description of problem:
Installation with a custom partitioning in kickstart fails with the following error:
Starting automated install................Saving storage configuration...
...Failed to save boot loader configuration
Failed to find a suitable stage1 device
Error in storage.log:
...
DEBUG:anaconda.modules.storage.bootloader.bootloader:Drive is set to 'sda'.
DEBUG:anaconda.modules.storage.bootloader.base:Is sda a valid stage1 target device?
DEBUG:anaconda.modules.storage.bootloader.base:stage1 device cannot be of type disk
DEBUG:anaconda.modules.storage.bootloader.base:Is sda1 a valid stage1 target device?
ERROR:anaconda.modules.storage.partitioning.base_partitioning:Bootloader configuration has failed: Failed to find a suitable stage1 device
INFO:anaconda.threading:Thread Failed: AnaTaskThread-CustomPartitioningTask-1 (140735433273504)
ERROR:anaconda.modules.common.task.task:Thread AnaTaskThread-CustomPartitioningTask-1 has failed: Traceback (most recent call last):
File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/partitioning/base_partitioning.py", line 54, in run
self._run(self._storage)
File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/partitioning/automatic/noninteractive_partitioning.py", line 43, in _run
self._setup_bootloader(storage)
File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/partitioning/automatic/noninteractive_partitioning.py", line 132, in _setup_bootloader
setup_bootloader(storage)
File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/bootloader/execution.py", line 44, in setup_bootloader
executor.execute(storage=storage, dry_run=dry_run)
File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/bootloader/execution.py", line 82, in execute
storage.bootloader.set_stage1_device(storage.devices)
File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/bootloader/base.py", line 612, in set_stage1_device
raise BootLoaderError(msg)
pyanaconda.modules.storage.bootloader.base.BootLoaderError: Failed to find a suitable stage1 device
Partitioning defined in the kickstart file:
zerombr
clearpart --all --initlabel
bootloader --location=mbr --leavebootorder
reqpart
part /boot --size 1000 --fstype=ext4
part pv.01 --grow --size 10000
volgroup vg pv.01
logvol / --grow --size=8000 --name=root --vgname=vg
logvol swap --fstype=swap --recommended --name=swap --vgname=vg
So far I've seen this problem on one ppc64le system.
Version-Release number of selected component (if applicable):
RHEL-9.0.0-20220210.0
anaconda-34.25.0.26-1.el9
python3-blivet-3.4.0-11.el9
How reproducible:
Always with the provided kickstart file on a specific system.
Steps to Reproduce:
1. Run a kickstart installation using the provided kickstart commands.
Actual results:
Installation fails, the installer is unable to find a suitable stage1 device.
Expected results:
Successful installation.
Comment 6RHEL Program Management
2023-08-15 07:28:26 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.