This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2208252 - Drivers from a DUD with the OEMDRV label are loaded twice
Summary: Drivers from a DUD with the OEMDRV label are loaded twice
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 2180394
TreeView+ depends on / blocked
 
Reported: 2023-05-18 11:37 UTC by Jan Stodola
Modified: 2024-01-17 04:25 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-18 16:33:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
journalctl with rd.debug (1.52 MB, text/plain)
2023-05-18 11:39 UTC, Jan Stodola 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-4779 0 None Migrated None 2023-09-18 16:33:31 UTC
Red Hat Issue Tracker RHELPLAN-157591 0 None None None 2023-05-18 11:38:20 UTC

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
Note You need to log in before you can comment on or make changes to this bug.