Description of problem:
Although srptools is present in RHEL 6 beta, and includes srp_daemon, srp_daemon.sh, and run_srp_daemon, it appears to be missing the init.d scripting to start this automatically at system boot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install the RHEL 6 Infiniband packages (ie srptools, rdma, various others)
2. Check in /etc/rdma, /etc/ofed, and /etc/init.d/* for scripting to automatically start the SRP HA daemon at boot time.
It doesn't seem to be present.
There should be a mechanism to automatically start the SRP daemon at boot time, possibly as part of the "rdma" init script (similar to how OFED works).
OFED does this via the /etc/init.d/openibd script, making use of an "SRPHA_ENABLE" variable (yes/no) in /etc/infiniband/openib.conf. Maybe a similar approach would be useful here, possibly inside the rdma init scripts?
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for 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. **
*** Bug 602948 has been marked as a duplicate of this bug. ***
Per Doug, moving to 6.1
FWIW, hooking this into the rdma startup script is the wrong place to do it. A script from another package should never be starting binaries from this package. A new script was created, srpd, and that service will now bring up the srp daemon at a point in the boot up sequence that is appropriate for a network block device. Please test this in your environment, I may need to adjust the startup sequence to work with devices that are automounted from /etc/fstab.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.