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:

I'm not quiet sure about whether a pid file is necessary in a running service, but since I followed the testing steps in BaseOS's InitScript testing wiki, I found that rdma doesn't have a pid file when service running. See this beaker link: https://beaker.engineering.redhat.com/jobs/10079 , in more detail, here: https://beaker.engineering.redhat.com/logs/2010/79/10079/18344/220165/605456///test_log-rdma-is-stopped-pid-file-exists.log

The corresponding code in tests/rdma/Sanity/initscript is:

SERVICE=rdma
<snip>
rlServiceStart $SERVICE
rlAssertExists "/var/run/$SERVICE.pid" "Pid file /var/run/$SERVICE.pid must exist"

Version-Release number of selected component (if applicable):
rdma-1.0-7.el6.noarch

How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

NOTABUG.  There is no daemon, and therefore no pid file to create.  The status portion of the rdma service is determined entirely by checking which kernel modules are loaded into the running kernel.  Furthermore, the rdma service doesn't even create a definable thread in the kernel when the modules are loaded, so it's not like we could hijack a kernel thread pid number for the purposes you requested. I think you'll just need to give the rdma service a pass on this test in your test framework. (But confirm with notting)