Description of problem: Failing systemctl calls: systemctl reload-or-restart rdma.service systemctl reload-or-try-restart rdma.service Version-Release number of selected component (if applicable): rdma-1.0-11.fc17.noarch systemd-44-4.fc17.x86_64 Steps to Reproduce: # systemctl status rdma.service rdma.service - LSB: Loads and unloads the InfiniBand and iWARP kernel modules Loaded: loaded (/etc/rc.d/init.d/rdma) Active: inactive (dead) since Tue, 24 Apr 2012 03:25:28 -0400; 24h ago Process: 5458 ExecStop=/etc/rc.d/init.d/rdma stop (code=exited, status=0/SUCCESS) Process: 28637 ExecReload=/etc/rc.d/init.d/rdma reload (code=exited, status=3/NOTIMPLEMENTED) Process: 4891 ExecStart=/etc/rc.d/init.d/rdma start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/rdma.service # systemctl start rdma.service # systemctl status rdma.service rdma.service - LSB: Loads and unloads the InfiniBand and iWARP kernel modules Loaded: loaded (/etc/rc.d/init.d/rdma) Active: active (exited) since Wed, 25 Apr 2012 04:04:22 -0400; 1s ago Process: 5458 ExecStop=/etc/rc.d/init.d/rdma stop (code=exited, status=0/SUCCESS) Process: 28637 ExecReload=/etc/rc.d/init.d/rdma reload (code=exited, status=3/NOTIMPLEMENTED) Process: 7516 ExecStart=/etc/rc.d/init.d/rdma start (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/rdma.service # systemctl reload-or-restart rdma.service Job failed. See system journal and 'systemctl status' for details. # echo $? 1 # systemctl reload-or-try-restart rdma.service Job failed. See system journal and 'systemctl status' for details. # echo $? 1 # systemctl restart rdma.service # echo $? 0 # Please consider fixing reload-or-restart and reload-or-try-restart functions. These are default systemd actions that do not need any implementation in the unit file by default. In this case they should both probably fall back to restart.
The rdma service doesn't have a daemon that keeps running, so a reload or restart is actually not really helpful. This wasn't picked up by default by systemd when dealing with the SysV init script. It was, however, easy to express to systemd once the unit file was written (Type=oneshot,RemainAfterExit=yes resolves this issue).
opensm-3.3.15-2.fc18, libibmad-1.3.9-1.fc18, libibumad-1.3.8-1.fc18, rdma-2.0-6.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/rdma-2.0-6.fc18,opensm-3.3.15-2.fc18,libibmad-1.3.9-1.fc18,libibumad-1.3.8-1.fc18
Package libibmad-1.3.9-1.fc18, libibumad-1.3.8-1.fc18, rdma-2.0-6.fc18, opensm-3.3.15-3.fc18, srptools-0.0.4-16.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libibmad-1.3.9-1.fc18 libibumad-1.3.8-1.fc18 rdma-2.0-6.fc18 opensm-3.3.15-3.fc18 srptools-0.0.4-16.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-19794/srptools-0.0.4-16.fc18,rdma-2.0-6.fc18,opensm-3.3.15-3.fc18,libibmad-1.3.9-1.fc18,libibumad-1.3.8-1.fc18 then log in and leave karma (feedback).
libibmad-1.3.9-1.fc18, libibumad-1.3.8-1.fc18, rdma-2.0-6.fc18, opensm-3.3.15-3.fc18, srptools-0.0.4-16.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.