Bug 2054636

Summary:	Bootloader configuration has failed: Failed to find a suitable stage1 device
Product:	Red Hat Enterprise Linux 9	Reporter:	Jan Stodola <jstodola>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0	CC:	jkonecny
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-15 07:28:26 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:
Bug Blocks:	1942219

Description Jan Stodola 2022-02-15 11:52:31 UTC

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 6 RHEL 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.