Bug 732151
| Summary: | nut-client in netclient mode causes a job failed error on startup | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | brian |
| Component: | nut | Assignee: | Michal Hlavinka <mhlavink> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 15 | CC: | mhlavink, sergey.kryzhny |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | nut-2.6.1-3.fc14 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-09-14 22:30:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Thanks, I've checked it and the code is even completely wrong, it won't report failure in some cases, where RETVAL=$? was after if test. nut-2.6.1-3.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/nut-2.6.1-3.fc14 nut-2.6.1-4.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/nut-2.6.1-4.fc15 Package nut-2.6.1-3.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing nut-2.6.1-3.fc14' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/nut-2.6.1-3.fc14 then log in and leave karma (feedback). *** Bug 736249 has been marked as a duplicate of this bug. *** nut-2.6.1-4.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. nut-2.6.1-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: The /etc/rc.d/init.d/ups script does not exit with a status 0 if the system is only running upsmon under the netclient mode. It appears that if running in one of the server modes RETVAL gets set initially but it never gets set if running as netclient since that portion of the script is skipped. Setting RETVAL to 0 at the beginning of the script appears to confirm this. The error is only a false positive - upsmon does run as expected. Version-Release number of selected component (if applicable): nut-client-2.6.1-3.fc15.x86_64 How reproducible: Install nut-client on a vanilla box and execute "service start ups". Steps to Reproduce: 1. 2. 3. Actual results: [root@bali etc]# service ups restart Restarting ups (via systemctl): Job failed. See system logs and 'systemctl status' for details. [FAILED] [root@bali etc]# echo $? 1 Expected results: [root@puppet-testbed init.d]# service ups start Starting ups (via systemctl): [ OK ] [root@puppet-testbed init.d]# echo $? 0 Additional info: