Bug 1044861

Summary: On OpenShift Enterprise 1.2 installation, oo-diagnostics -v -w 1 complains about cgroups
Product: OpenShift Container Platform Reporter: Jan Pazdziora <jpazdziora>
Component: ContainersAssignee: Luke Meyer <lmeyer>
Status: CLOSED WONTFIX QA Contact: libra bugs <libra-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.2.1CC: bleanhar, jpazdziora, libra-onpremise-devel, lmeyer
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-21 19:40:04 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jan Pazdziora 2013-12-19 06:40:27 UTC
Description of problem:

On a fresh all-on-one OpenShift Enterprise 1.2 installation, running oo-diagnostics -v -w 1 fails with

INFO: running oo-accept-node
[31mFAIL: run_script
oo-accept-node had errors:
--BEGIN OUTPUT--
FAIL: lscgroup /openshift path does not exist
1 ERRORS

--END oo-accept-node OUTPUT--[0m
INFO: running: test_broker_httpd_error_log
INFO: running: test_broker_passenger_ps
INFO: checking the broker application process tree
INFO: running: test_for_nonrpm_rubygems
INFO: checking for presence of gem-installed rubygems
INFO: looking in /opt/rh/ruby193/root/usr/local/share/gems/specifications/*.gemspec /opt/rh/ruby193/root/usr/share/gems/specifications/*.gemspec
INFO: running: test_for_multiple_gem_versions
INFO: checking for presence of gem-installed rubygems
INFO: running: test_node_httpd_error_log
INFO: running: test_node_containerization_plugin
INFO: running: test_node_mco_log
INFO: running: test_pam_openshift
INFO: running: test_services_enabled
INFO: checking that required services are running now
[31mFAIL: test_services_enabled
      The following service(s) are not currently started:
        openshift-cgroups
      These services are required for OpenShift functionality.
[0m
INFO: checking that required services are enabled at boot

Version-Release number of selected component (if applicable):

1.2

How reproducible:

Not deterministic.

Steps to Reproduce:
1. Run ./openshift.sh to configure all on one Enterprise 1.2.
2. Run oo-diagnostics -v -w 1

Actual results:

INFO: running oo-accept-node
[31mFAIL: run_script
oo-accept-node had errors:
--BEGIN OUTPUT--
FAIL: lscgroup /openshift path does not exist
1 ERRORS

--END oo-accept-node OUTPUT--[0m
INFO: running: test_broker_httpd_error_log
INFO: running: test_broker_passenger_ps
INFO: checking the broker application process tree
INFO: running: test_for_nonrpm_rubygems
INFO: checking for presence of gem-installed rubygems
INFO: looking in /opt/rh/ruby193/root/usr/local/share/gems/specifications/*.gemspec /opt/rh/ruby193/root/usr/share/gems/specifications/*.gemspec
INFO: running: test_for_multiple_gem_versions
INFO: checking for presence of gem-installed rubygems
INFO: running: test_node_httpd_error_log
INFO: running: test_node_containerization_plugin
INFO: running: test_node_mco_log
INFO: running: test_pam_openshift
INFO: running: test_services_enabled
INFO: checking that required services are running now
[31mFAIL: test_services_enabled
      The following service(s) are not currently started:
        openshift-cgroups
      These services are required for OpenShift functionality.
[0m
INFO: checking that required services are enabled at boot

Expected results:

No error.

Additional info:

A couple of minutes later, all is fine, no errors and warnings. So it looks like some timing issue.

I should note that I start OpenShift with

for i in activemq mcollective ruby193-mcollective mongod $(cd /etc/init.d && ls openshift-*) cgconfig cgred oddjobd httpd ; do echo $i ; service $i restart ; done

(run twice) because I really cannot do reboot.

So maybe just waiting for something to be properly initialized would help?

Comment 3 Luke Meyer 2013-12-19 22:59:50 UTC
That didn't use to happen. I'll have to figure out what changed.

Comment 4 Luke Meyer 2013-12-20 21:11:08 UTC
I'm wondering if this is related to not rebooting. The instructions are always to reboot after install. Obviously, anything aside from a kernel update should be possible to do without the reboot, but we haven't pursued the instructions to start everything reliably without it.

Comment 5 Jan Pazdziora 2013-12-22 09:55:08 UTC
It can be related to not rebooting. But I did not see this with 1.2 a couple of months ago (without reboot again) so I assume something changed in openshift.sh since then ...