Red Hat Bugzilla – Bug 902630
Failed to reload openshift-broker service
Last modified: 2017-03-08 12:34 EST
Description of problem: Reload openshift-broker service, it returns " Reloading openshift-broker: not reloading due to configuration syntax error [FAILED] Version-Release number of selected component (if applicable): http://download.lab.bos.redhat.com/rel-eng/OpenShiftEnterprise/1.1/2013-01-17.1/ How reproducible: Always Steps to Reproduce: 1. Reload openshift-broker service [root@broker init.d]# ./openshift-broker reload 2. Force-reload openshift-broker service Actual results: RESULT: 1. [root@broker init.d]# ./openshift-broker reload Reloading openshift-broker: not reloading due to configuration syntax error [FAILED] 2. [root@broker init.d]# service openshift-broker force-reload Reloading openshift-broker: not reloading due to configuration syntax error [FAILED] Expected results: Success Additional info:
Here's one possible fix: https://github.com/openshift/origin-server/pull/1192
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/b23cd598c04154806456320929b50d04878b24c2 Bug 902630: fix `service openshift-broker reload` In the initscript, the options to give to httpd are stored in the $OPTIONS variable. In the current version of the script, the status action has an error that causes $OPTIONS to be expanded incorrectly. This commit resolves the issue by using eval, set, and "$@" to coax BASH into performing the expansion we want. This commit also fixes an unrelated issue: The reload action did not print anything on success, and now it will. This commit should fix Bug 902630.
Note that the above fix has been merged into origin-server, but not into enterprise-server.
This fix shipped in the last puddle: http://buildvm-devops.usersys.redhat.com/puddle/build/OpenShiftEnterprise/1.1.x/2013-01-29.1/
Verified this bug with 1.1.x/2013-01-29.1 puddle, and PASS. # /etc/init.d/openshift-broker reload Reloading openshift-broker: [ OK ]
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0582.html