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:

The issue mentioned in the bug 1094538 still exists in 7.2. The file usr/lib/udev/rules.d/98-rdma.rules should have the following rule:


SUBSYSTEM=="module", KERNEL=="usnic_verbs", ACTION=="add", TAG+="systemd", ENV{SYSTEMD_WANTS}="rdma.service"


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
rdma service should be launched if the usnic_verbs kernel module present

Additional info:
refer to bug 1094538

This is the wrong order of execution.  The rdma service loads the usnic_verbs kernel module, not the other way around.  In order to trigger the rdma service, we use the presence of the enic module.  This is because the only thing reliably loaded based upon PCI IDs is the enic module.  If you check the udev rules file for rdma, you see that it includes a line for starting the service in the presence of the enic module.  If you check the rdma start script, you will see this snippet:

if is_module enic -a ! is_module usnic_verbs; then
  load_modules usnic_verbs
  RC+=$?
fi

As you can see, the rdma service loads the usnic_verbs module, so starting the rdma service on the presence of the usnic_verbs module would create a circular dependency and cause the init sequence to fail.