Bug 1865851

Summary:	Anaconda does not detect and use a ks.cfg on a disk labeled OEMDRV
Product:	Red Hat Enterprise Linux 8	Reporter:	jcastran
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	jstodola
Target Milestone:	rc
Target Release:	8.0
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:	2020-08-04 14:14:41 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:

Description jcastran 2020-08-04 11:22:55 UTC

Description of problem:
RHEL 8 does not use a kickstart (ks.cfg) located on a drive labeled OEMDRV

Version-Release number of selected component (if applicable):
8.2

How reproducible:
Everytime

Steps to Reproduce:
1.Create a drive labeled OEMDRV and place a valid kickstart on it (ks.cfg)
2. Boot the installation with the OEMDRV connected
3.

Actual results:
Manual installation, no ks.cfg fouund in the installation environment

Expected results:
Anaconda should automatically find ks.cfg in drives labeled OEMDRV and apply it to the installation.

Additional info:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/performing_an_advanced_rhel_installation/index#making-a-kickstart-file-available-on-a-local-volume-for-automatic-loading_making-kickstart-files-available-to-the-installation-program

Comment 1 Jan Stodola 2020-08-04 11:43:07 UTC

This could be a duplicate of bug 1770969. Could you please add "rd.debug" on the kernel command line when starting the installation and see if it helps as a workaround?

Comment 2 jcastran 2020-08-04 14:14:41 UTC


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