Bug 804892

Summary: Return "Node execution failure" when reload a running jenkins application
Product: OKD Reporter: bzhao
Component: ContainersAssignee: Dan McPherson <dmcphers>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.xCC: ccoleman, dmcphers, rmillner, xtian
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: devenv_1666 and stage Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-13 18:31:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
jenkins_log none

Description bzhao 2012-03-20 05:21:05 UTC 
Description of problem:
It'll return "Node execution failure (invalid exit code from node).  If the problem persists please contact Red Hat support." when reload a running jenkins application

Version-Release number of selected component (if applicable):
rhc-0.88.9-1.el6_2.noarch

How reproducible:
Always

Steps to Reproduce:
1.Create a jenkins application
# rhc-create-app -t jenkins-1.4 -p xxx -a jenkinstest
2.Make sure jenkins application is running 
# rhc-ctl-app -c status -p xxx -a jenkinstest
3.Reload the jenkins application
# rhc-ctl-app -c reload -p xxx -a jenkinstest
  
Actual results:
It'll return "Node execution failure (invalid exit code from node).  If the problem persists please contact Red Hat support."

Expected results:
The jenkins application could be reloaded successfully without any error

Additional info:
Comment 1 bzhao 2012-03-20 05:22:30 UTC 
Created attachment 571288 [details]
jenkins_log
Comment 2 bzhao 2012-03-20 07:02:25 UTC 
Version-Release number of selected component:
rhc-cartridge-jenkins-1.4-0.89.1
rhc-cartridge-jenkins-client-1.4-0.23.1.el6_2.noarch
Comment 3 bzhao 2012-03-21 09:30:59 UTC 
It's fixed on devenv_1668, but the fix isn't pushed to stage
Comment 4 Dan McPherson 2012-03-21 14:02:10 UTC 
Thanks.  For some reason it wasn't installed yesterday in stage.
Comment 5 bzhao 2012-03-23 07:40:41 UTC 
Passed verification on devenv-1669