Bug 1009234

Summary: Installing aerogear/openshift-origin-cartridge-aerogear-push fails
Product: OpenShift Container Platform Reporter: Jan Pazdziora <jpazdziora>
Component: ContainersAssignee: Jason DeTiberus <jdetiber>
Status: CLOSED WONTFIX QA Contact: libra bugs <libra-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.2.0CC: bleanhar, jpazdziora, libra-onpremise-devel
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1009236 1009237 (view as bug list) Environment:
Last Closed: 2014-03-21 19:37:34 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:
Bug Depends On: 1009236, 1009237    
Bug Blocks:    

Description Jan Pazdziora 2013-09-18 03:39:13 UTC 
Description of problem:

I try to deploy

https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push

on my OpenShift Enterprise 1.2 all-on-one installation. The rhc app create command fails.

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

# rpm -qa 'openshift*' | sort
openshift-origin-broker-1.5.8-1.el6op.noarch
openshift-origin-broker-util-1.9.10-1.el6op.noarch
openshift-origin-cartridge-cron-1.7.6-1.1.el6op.noarch
openshift-origin-cartridge-diy-0.4.8-1.1.el6op.noarch
openshift-origin-cartridge-haproxy-0.4.11-1.el6op.noarch
openshift-origin-cartridge-jbosseap-2.3.11.1-1.el6op.noarch
openshift-origin-cartridge-jbossews-0.4.9-1.el6op.noarch
openshift-origin-cartridge-jenkins-1.9.8-1.el6op.noarch
openshift-origin-cartridge-jenkins-client-1.8.6-1.1.el6op.noarch
openshift-origin-cartridge-mysql-0.3.7-1.el6op.noarch
openshift-origin-cartridge-perl-0.4.8.2-1.el6op.noarch
openshift-origin-cartridge-php-0.4.9.2-1.el6op.noarch
openshift-origin-cartridge-postgresql-0.2.7-1.1.el6op.noarch
openshift-origin-cartridge-python-0.4.8.1-1.el6op.noarch
openshift-origin-cartridge-ruby-0.4.10.3-1.el6op.noarch
openshift-origin-console-1.5.24-1.el6op.noarch
openshift-origin-msg-common-1.7.2-1.1.el6op.noarch
openshift-origin-msg-node-mcollective-1.9.3-1.1.el6op.noarch
openshift-origin-node-proxy-0.9.2-1.1.el6op.noarch
openshift-origin-node-util-1.9.9.2-1.el6op.noarch
openshift-origin-port-proxy-1.6.4-1.el6op.noarch
openshift-origin-util-scl-1.4.1-1.1.el6op.noarch

How reproducible:

Deterministic.

Steps to Reproduce:
1. Have OpenShift Enterprise 1.2 installed.
2. Run rhc app create aerog https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push mysql-5.1

Actual results:

The cartridge 'https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push' will be
downloaded and installed

Application Options
-------------------
  Namespace:  test
  Cartridges: https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push, mysql-5.1
  Gear Size:  default
  Scaling:    no

Creating application 'aerog' ... 
Unable to complete the requested operation due to: Node execution failure (invalid exit code from node).  If the problem persists please
contact Red Hat support..
Reference ID: 286b75120e090c2681f8c41cd1c53531

Expected results:

No error, cartridge deployed.

Additional info:
Comment 1 Jan Pazdziora 2013-09-18 03:40:24 UTC 
Clayton looked at the machine and found

September 17 10:12:45 DEBUG Shell command 'cgset -r cpu.cfs_quota_us=100000 /openshift/5238632e6892dffbd
60000d6' ran. rc=0 out=
September 17 10:12:45 DEBUG 5238632e6892dffbd60000d6 start against 'aerogear-push'
September 17 10:14:24 DEBUG Shell command '/sbin/runuser -m -s /bin/sh 5238632e6892dffbd60000d6 -c "exec
 /usr/bin/runcon 'unconfined_u:system_r:openshift_t:s0:c2,c212' /bin/sh -c \"set -e; /var/lib/openshift/5238632e6892dffbd60000d6/aerogear-push/bin/control start\""' ran. rc=1 ou
t=Starting aerogear-push cart
Timed out waiting for http listening port

in the platform.log as the culprit.

He says: I don't know whether this is a timeout issue caused by cgroups (not enough CPU, start didn't complete in the requisite time allowed by the platform), or another error in.

This bugzilla is about the cartridge not installing properly.