Bug 2208252

Summary: Drivers from a DUD with the OEMDRV label are loaded twice
Product: Red Hat Enterprise Linux 8 Reporter: Jan Stodola <jstodola>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED MIGRATED QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.8CC: jkonecny, msekleta
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
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-09-18 16:33:38 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: 2180394    
Attachments:
Description Flags
journalctl with rd.debug none

Description Jan Stodola 2023-05-18 11:37:40 UTC
Description of problem:
Drivers from a DUD with the OEMDRV label are loaded twice:

...
[  OK  ] Reached target Basic System.
[   13.305658] dracut-initqueue[1268]: DD: Examining /dev/sr1
[   13.356371] dracut-initqueue[1269]: mount: /media/DD-1: WARNING: device write-protected, mounted read-only.
[   13.367248] dracut-initqueue[1268]: DD: Extracting: kmod-redhat-e1000e
[   13.386035] dracut-initqueue[1268]: DD: Extracting: kmod-redhat-e1000
[   15.663846] dracut-initqueue[1305]: DD: Examining /dev/sr1
[   15.718236] dracut-initqueue[1306]: mount: /media/DD-2: WARNING: device write-protected, mounted read-only.
[   15.727938] dracut-initqueue[1305]: DD: Extracting: kmod-redhat-e1000e
[   15.748941] dracut-initqueue[1305]: DD: Extracting: kmod-redhat-e1000
[   18.212683] dracut-initqueue[1352]: Warning: Can't get kickstart from /dev/sr1:/ks.cfg
[   18.258722] dracut-initqueue[1380]: Warning: Can't get kickstart from /dev/sr1:/ks.cfg
[  OK  ] Started dracut initqueue hook.
[  OK  ] Reached target Remote File Systems (Pre).
...

Version-Release number of selected component (if applicable):
RHEL-8.8, anaconda-33.16.8.9-1.el8_8

How reproducible:
always

Steps to Reproduce:
1. Have a DUD with the OEMDRV label. (Use a DUD containing drivers which are not needed by the system, for example the e1000e driver on a VM with virtio network device. This is to avoid another problem with reloading drivers described in bug 1729032.)
2. Attach the DUD as a CDROM device and boot the system.

Actual results:
DUD is examined and drivers loaded twice.

Expected results:
DUD is examined and drivers loaded just once.

Additional info:
Possible related bugs are:
Bug 1700368 - Drivers from driverdisk in kickstart are loaded several times
Bug 1729032 - Driver update end up in infinite loop when driver of storage device which contains driverdisc is updated.

Comment 1 Jan Stodola 2023-05-18 11:39:19 UTC
Created attachment 1965413 [details]
journalctl with rd.debug

Comment 3 Jan Stodola 2023-05-18 12:10:40 UTC
Just a note that this problem can be also reproduced on RHEL-8.9 with anaconda-33.16.9.1-1.el8, but I didn't see it on RHEL-9.2/9.3, where the DUD is examined just once.

Comment 4 Jiri Konecny 2023-05-25 08:45:57 UTC
Hi Michale, could you please take a look on this. I'm not sure what is happening but based on the logs I think we are generating one rule for udev with function `when_diskdev_appears` for OEMDRV label.

However, for some reason it seems to be executed twice

//lib/dracut/hooks/initqueue/settled/driver-updates878.sh
//lib/dracut/hooks/initqueue/settled/driver-updates906.sh

IIRC we are calling settled but that didn't caused issues before. Did something changed recently in udev what could cause this behavior?

Comment 5 RHEL Program Management 2023-09-18 16:31:54 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-18 16:33:38 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 7 Red Hat Bugzilla 2024-01-17 04:25:33 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days