Bug 785514

Description of problem:
when trying create app with "--enable-jenkins" option, it ended up with "Node execution failure" when embedding jenkins client into app.
but manually embedding jenkins client via rhc-ctl-app -e works well as expected.

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

How reproducible:
always

Steps to Reproduce:
1. create a domain without any other app
2. create app with "--enable-jenkins" option
3.
  
Actual results:
Failed to create app

Expected results:
Succeeded to create app

Additional info:
[root@intel-q8200novt-8-6 test]# rhc app create -a test -t php-5.3 --enable-jenkins -d
Password: 
Submitting form:
debug: true
rhlogin: lilu+6
Contacting https://ec2-50-17-132-84.compute-1.amazonaws.com
Creating application: jenkins
Contacting https://ec2-50-17-132-84.compute-1.amazonaws.com
Response from server:
DEBUG:
fold: write error: Broken pipe
fold: write error: Broken pipe

Exit Code: 0
broker_c: namespacerhloginsshapp_uuiddebugaltercartridgecart_typeactionapp_nameapi
api_c: placeholder
API version:    1.1.2
Broker version: 1.1.1
DEBUG: 'jenkins' creation returned success.
Now your new domain name is being propagated worldwide (this might take a minute)...

Note: There is a git repo for your Jenkins application 'jenkins'
but it isn't being downloaded as part of this process.  In most cases
it isn't needed but you can always clone it later.

Confirming application 'jenkins' is available
  Attempt # 1
Confirming application 'jenkins' is available:  Success!

jenkins published:  http://jenkins-lilu6.dev.rhcloud.com/
git url:  ssh://809a1b76b6d24fbf94d6ae6f696f6928.rhcloud.com/~/git/jenkins.git/
To make changes to 'jenkins', you must first clone it with:
      git clone ssh://809a1b76b6d24fbf94d6ae6f696f6928.rhcloud.com/~/git/jenkins.git/

Then run 'git push' to update your OpenShift Express space.

Jenkins created successfully.  Please make note of these credentials:

   User: admin
   Password: 7kXD7hk3PmCZ

Note:  You can change your password at: http://jenkins-lilu6.dev.rhcloud.com/me/configure

Creating application: test
Contacting https://ec2-50-17-132-84.compute-1.amazonaws.com
Response from server:
DEBUG:
Initialized empty Git repository in /var/lib/libra/681ebe75f0b740e1801f6ffce6c6955d/git/test.git/

Exit Code: 0
broker_c: namespacerhloginsshapp_uuiddebugaltercartridgecart_typeactionapp_nameapi
api_c: placeholder
API version:    1.1.2
Broker version: 1.1.1
DEBUG: 'test' creation returned success.
Now your new domain name is being propagated worldwide (this might take a minute)...
Pulling new repo down
git clone --quiet ssh://681ebe75f0b740e1801f6ffce6c6955d.rhcloud.com/~/git/test.git/ test
Warning: Permanently added 'test-lilu6.dev.rhcloud.com,50.17.132.84' (RSA) to the list of known hosts.
remote: Counting objects: 16, done.
remote: Compressing objects: 100% (11/11), done.
remote: Total 16 (delta 1), reused 16 (delta 1)
Receiving objects: 100% (16/16), 13.84 KiB, done.
Resolving deltas: 100% (1/1), done.
Now embedding the jenkins client into 'test'...
Contacting https://ec2-50-17-132-84.compute-1.amazonaws.com
Problem reported from server. Response code was 500.

DEBUG:
Cartridge return code: 1

Exit Code: 1
broker_c: namespacerhloginsshapp_uuiddebugaltercartridgecart_typeactionapp_nameapi
api_c: placeholder
API version:    1.1.2
Broker version: 1.1.1

RESULT:
Node execution failure (invalid exit code from node).  If the problem persists please contact Red Hat support.

Cleaning up git repo
Cleaning up application
Contacting https://ec2-50-17-132-84.compute-1.amazonaws.com
Cleaning up application
Contacting https://ec2-50-17-132-84.compute-1.amazonaws.com