scl-utils is not properly installing, causing openshift-node-web-proxy to fail to start #303
Comments
|
@mikeSGman I believe this to be a packaging issue rather than a puppet issue. Working backwards from openshift-origin-node-proxy package, which provides the openshift-node-web-proxy init script, I get the following dependency chain which should ensure proper installation. openshift-origin-node-proxy -> nodejs010-nodejs -> nodejs010-runtime -> /usr/bin/scl_source which is provided by scl-utils package. Are you able to reproduce this issue? |
|
With my OP being an older comment, you might be correct as the puppet pieces have changed measurably since then. I will rebuild and see if it still happens. Thanks for the feedback @sdodson |
|
I am using this repo: experiencing same issue. |
Centos 6.5 install of OSO M4
This has been tested with an OOB CentOS 6.5 VM running oo-install using OSO Release 4 (M4) repos.
excerpt of oo-diagnostics -vv:
FAIL: test_services_enabled
The following service(s) are not currently started:
openshift-node-web-proxy
These services are required for OpenShift functionality.
Service checking as reported by oo-diagnostics -vv:
[root@broker ~]# service openshift-node-web-proxy restart
Stopping node-web-proxy: [ OK ]
Starting node-web-proxy: /opt/rh/nodejs010//enable: line 5: scl_source: No such file or directory
This fixes the issue:
yum -y install scl-utils-20120927-9.el6oso.x86_64
Finally:
[root@broker ~]# service openshift-node-web-proxy restart
Stopping node-web-proxy: [ OK ]
Starting node-web-proxy: [ OK ]
The text was updated successfully, but these errors were encountered: