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.