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.

Description of problem:

A customer using HP Ethernet 10Gb 2-port 530SFP+ Adapter cannot install systems through the network, because the NIC doesn't manage to auto-negotiate the speed.
On RHEL7.9, I gave him a custom initrd including ethtool and associated code to read new kernel parameters that get processed by ethtool just after setting the link up:

  e.g.

    ethtool.eth0=autoneg:off,speed:1000 ethtool.eth1=autoneg:off,speed:1000


On RHEL8, NetworkManager is used, so we need a similar enhancement. Of course the syntax above is just a proposal, maybe NM-like settings would be preferred here.


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

RHEL8.x x>=0


How reproducible:

Always on customer hardware (no way to boot).

NetworkManager uses nm-initrd-generator which parses the command line. 
That basically implements some parts of `man dracut.cmdline`.

The command line options we add should also be agreed upon with dracut (and documented in dracut.cmdline).

It may not be required that dracut's "network" module also implements this API (as I think it's unavoidable that certain features only work with certain modules). But in principle that should be possible and would be nice to have.


CC-ing Lukas [FYI]

I am fine with that. And as you mention, I don't think we need this in the legacy network.

NM unit test added.

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 (Moderate: NetworkManager security, 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/RHSA-2021:4361