Bug 1968118

Created attachment 1789073 [details]
Screenshot of the udev database when booting the 8.4 DVD

Created attachment 1789074 [details]
udev database after installing (more recent kernel)

Sorry, this is pure systemd, seems like.

(In reply to Renaud Métrich from comment #3)
> Sorry, this is pure systemd, seems like.

I doubt that. It is something with the installer environment. Either /usr/lib/udev/hwdb.d/20-net-ifname.hwdb is missing or systemd-hwdb-update.service has not been run before systemd-udevd.service is started (.hwdb files are not used by systemd-udevd directly. They must be compiled into binary format first--the file is /etc/udev/hwdb.bin). The former is the case in initrd, because no hwdb files are installed there, but the interface should still be correctly renamed after switch-root (that is what happens on the installed system too, after all).

Besides, there weren't any significant changes in udev between 8.2 and 8.3.

I checked with the 8.4 installation DVD and it seems this should work...

# systemd-hwdb query usb:v413CpA102
ID_VENDOR_FROM_DATABASE=Dell Computer Corp.
ID_MODEL_FROM_DATABASE=iDRAC Virtual NIC
ID_NET_NAME_FROM_DATABASE=idrac

Can we see boot logs?

Moving to NetworkManager since issue is due to using it in the initramfs during installation.

please provide debug logs of NetworkManager (or better, the full boot).

I think you do that via `rd.debug` on the kernel command line.

Still waiting on more info. Let's move to rhel-8.6

In initrd there is a "Wired Connection" compatible only with device
eno1, because of command line argument "ksdevice=98:03:9b:98:41:36"
which gets translated into "BOOTIF=01-98-03-9b-98-41-36". So, only
eno1 gets activated; however also other devices (eno2, enp0s20f0u14u3)
are brought up.

We should probably introduce a configuration option to treat as
unmanaged all devices without a candidate connection, and enable that
option via a configuration snippet in initrd.

(In reply to Beniamino Galvani from comment #14)
>
> We should probably introduce a configuration option to treat as
> unmanaged all devices without a candidate connection, and enable that
> option via a configuration snippet in initrd.

bug 1650221

Removing from the RPL based on lack of voting from all parties (CEE, Dev, QE). Please add it back if there is agreement to get it on the RPL.

Thanks!
Sushil

I'm now convinced this is not a NetworkManager problem.

Sure, it would be nice if NetworkManager wouldn't bring up devices it is not configuring, but that wouldn't happen here, because at the time the network is configured for kickstart to be fetched, NetworkManager can't tell that it shouldn't be bringing up the iDRAC interface up.

The interface renaming is supposed to (and in fact always happens) early in the iniramfs, prior to NetworkManager being started.

I've proposed a fix upstream and am going to be reassiging the bug to dracut developers to take a look:
https://github.com/dracutdevs/dracut/pull/1681

In case this needs a workaround, the customer can put something like this into their kickstart file (the pykickstart documentation suggests the %pre sections need to go at the end):

%pre
set -x
trig() { udevadm trigger --action=add --property-match=ID_NET_NAME_FROM_DATABASE=idrac $*; }
ip link set $(trig -v -n |xargs basename) down
trig --settle
%end

(In reply to Lubomir Rintel from comment #22)
As I'm facing the same problem on a Dell R640 (usig PXE Boot of 8.6), I tried the proposed work-around, but had to change it as follows:

%pre
set -x
trig() { udevadm trigger --action=add --property-match=ID_NET_NAME_FROM_DATABASE=idrac $*; }
for d in $(trig -v -n | xargs basename -a); do
    ip link set "$d" down
done
trig # using --settle hangs forever
%end

(In reply to Andreas Luik from comment #28)
> (In reply to Lubomir Rintel from comment #22)
> As I'm facing the same problem on a Dell R640 (usig PXE Boot of 8.6), I
> tried the proposed work-around, but had to change it as follows:
> 
> %pre
> set -x
> trig() { udevadm trigger --action=add
> --property-match=ID_NET_NAME_FROM_DATABASE=idrac $*; }
> for d in $(trig -v -n | xargs basename -a); do
>     ip link set "$d" down
> done
> trig # using --settle hangs forever
> %end

I also had similar issue on PowerEdge R650 with 8.5 kickstart. I used this workaround successfully.

Tested & posted the fix upstream; prepared PR downstream: https://github.com/redhat-plumbers/dracut-rhel8/pull/27

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 (dracut 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.

https://access.redhat.com/errata/RHBA-2023:7087