Bug 2171811

Summary: OEMDRV not being detected on USB devices
Product: Red Hat Enterprise Linux 9 Reporter: Renaud Métrich <rmetrich>
Component: anacondaAssignee: Jiri Konecny <jkonecny>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact: Sagar Dubewar <sdubewar>
Priority: high    
Version: 9.0CC: bwelterl, cbesson, gfialova, jkonecny, jstodola, kasmith, kmarutha, linux-bugs, narendra_k, rvykydal, sbarcomb, sdubewar, sroza, stuart_hayes, Vinay_Hm
Target Milestone: rcKeywords: Triaged
Target Release: 9.3   
Hardware: All   
OS: Linux   
Fixed In Version: anaconda- Doc Type: Enhancement
Doc Text:
.New boot option `inst.wait_for_disks=` to add wait time for loading a Kickstart file or the kernel drivers Sometimes, it may take a few seconds to load a Kickstart file or the kernel drivers from the device with the `OEMDRV` label during the boot process. To adjust the wait time, you can now use the new boot option, `inst.wait_for_disks=`. Using this option, you can specify how many seconds to wait before the installation. The default time is set to `5` seconds, however, you can use `0` seconds to minimize the delay. For more information about this option, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html-single/boot_options_for_rhel_installer/index#storage-boot-options_kickstart-and-advanced-boot-options[Storage boot options].
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-07 08:31:56 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:
Bug Depends On:    
Bug Blocks: 2186840    

Description Renaud Métrich 2023-02-20 13:47:02 UTC
Created attachment 1945277 [details]
Log of the boot reproducing while having "rd.debug"

This bug was initially created as a copy of Bug #1770969

I am copying this bug because: 

This still happens on Dell hardware with RHEL9

Description of problem:

When using a USB-based driver-disk with a filesystem labeled "OEMDRV" containing a ks.cfg file, the installer does not recognize it.
Adding some delays, ie. "rd.debug", the device gets recognized and the ks.cfg of that device is used, but it's not reliable, the customer can reproduce even with "rd.debug".

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


How reproducible:

Always on customer Hardware

Steps to Reproduce:
1. Create a OEMDRV image or filesystem on a USB device, place some minimal ks.cfg on this.
2. Attach this OEMDRV device as USB device to a KVM machine
3. Start the installation using "rhel-9.0-x86_64-dvd.iso"

Actual results:

ks.cfg is not loaded, graphical installer is shown

Expected results:

ks.cfg is loaded, using instructions as per ks.

Comment 3 Renaud Métrich 2023-03-02 08:51:10 UTC

I'm submitting PR https://github.com/rhinstaller/anaconda/pull/4586 to deal with this.
It adds a default delay of 5 seconds for disks to appear, so that we are sure OEMDRV, if present, is taken into account.

The original behaviour can be restored through booting with `rd.disks_delay=0`.

This is still work in progress, please comment in the PR for changes.


Comment 8 Jiri Konecny 2023-04-28 13:25:35 UTC
PR: https://github.com/rhinstaller/anaconda/pull/4720

Comment 9 Jan Stodola 2023-05-17 09:53:45 UTC
Tested with anaconda-

When inst.wait_for_disks=0 was present on the kernel cmdline, the problem could be reproduced occasionally.
Without inst.wait_for_disks the installer waited ~5 seconds and then continued, as expected. The problem is no longer reproducible.
Tested also inst.wait_for_disks=30, which waited ~30 seconds during the boot process.

Marking as Verified:Tested

Comment 10 Jan Stodola 2023-05-17 12:08:54 UTC
Removing Verified:Tested, since a possible issue has been found and additional tests are running.

Comment 11 Jan Stodola 2023-05-18 12:32:16 UTC
Marking as Verified:Tested, no new problem was discovered during additional testing. (See RHEL-8 bug 1770969 for more info.)

Comment 15 Jan Stodola 2023-05-26 07:26:49 UTC
FYI, a new regression appeared, possibly caused by this change. See bug 2209599.

Comment 17 Jan Stodola 2023-06-01 09:18:38 UTC
*** Bug 2164324 has been marked as a duplicate of this bug. ***

Comment 21 Jan Stodola 2023-06-16 09:29:37 UTC
I'm moving this bug to VERIFIED, bug 2209599 has a fix and no regression has been found for this bug.

This bug fix should be documented in the release notes. A doc text has been proposed in bug 1770969 for review. Once this is done, it can be copied to this bug as well. Setting needinfo on Sagar to copy the text here once it is approved.

Also bug 2215506 was reported to document the new boot option in the installation guide.

Comment 25 errata-xmlrpc 2023-11-07 08:31:56 UTC
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 (anaconda bug fix and enhancement update), and where to find the updated
files, follow the link below.

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