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:
rlAssertExists "/var/run/$SERVICE.pid" "Pid file /var/run/$SERVICE.pid must exist"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
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)