Skip to content
This repository has been archived by the owner on Aug 29, 2018. It is now read-only.

scl-utils is not properly installing, causing openshift-node-web-proxy to fail to start #303

Open
mikeSGman opened this issue Sep 27, 2014 · 3 comments
Labels

Comments

@mikeSGman
Copy link

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 ]

@sdodson sdodson added the bug label Nov 12, 2014
@sdodson
Copy link
Member

sdodson commented Nov 19, 2014

@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?

@mikeSGman
Copy link
Author

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

@EssentialMix
Copy link

I am using this repo:
repos_base => 'https://mirror.openshift.com/pub/origin-server/release/4/rhel-6',
optional_repo => 'http://download.fedoraproject.org/pub/epel/6/$basearch',

experiencing same issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants