Bug 820822

Summary:	Can not create jboss application through website and CLI on stage sometimes
Product:	OKD	Reporter:	Yujie Zhang <yujzhang>
Component:	Containers	Assignee:	Bill DeCoste <wdecoste>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.x	CC:	bmeng, rmillner, xtian
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-14 17:22:45 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:
Embargoed:

Description Yujie Zhang 2012-05-11 04:58:46 UTC

Description of problem:

When I try to create jboss applciation, it will redirect to page which says "We're sorry.....".
On CLI ,error message will come out which says "Node execution failure (invalid exit code from node).  If the problem persists please contact Red Hat support.
"

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

stage.openshift.redhat.acom

How reproducible:always


Steps to Reproduce:
1.Go to openshift website and login
2.Try to create jboss application on website
3."rhc-create-app -a jboss1 -t jbossas-7 -l $account"
  
Actual results:

Can not create jboss application through website and CLI on stage.

Expected results:

JBoss application should be created correctly.

Additional info:

Comment 1 Yujie Zhang 2012-05-11 05:50:33 UTC

For the proxy is working again ,we can create jboss application now, so close this bug.

Comment 2 Yujie Zhang 2012-05-11 09:28:06 UTC

This issue happens randomly,so reopen this bug and lower the priority.

Comment 3 Yujie Zhang 2012-05-11 09:28:58 UTC

This issue happens randomly,so reopen this bug and lower the priority.

Comment 4 Xiaoli Tian 2012-05-11 11:30:13 UTC

Actually, not sometimes fail, but sometimes succeed or give a rough estimate: 50% fail and 50% success

Comment 5 Bill DeCoste 2012-05-11 17:39:14 UTC

Increased timeout for JBoss's HTTP to come up. Was 20s and is now 60s. If HTTP doesnt come up in this time, a 121 is returned.

Comment 6 Meng Bo 2012-05-14 06:11:50 UTC

verified on latest stage env,
issue has been fixed.