Bug 787119

Summary:	Failed to thread dump ruby app with ruby client
Product:	OKD	Reporter:	Xiaoli Tian <xtian>
Component:	oc	Assignee:	Bill DeCoste <wdecoste>
Status:	CLOSED CURRENTRELEASE	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.x	CC:	bmeng
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-02-17 02:07:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Xiaoli Tian 2012-02-03 08:37:10 UTC

Description of problem:

Encountered" Node execution failure (invalid exit code from node).  If the problem persists please contact Red Hat support" while trying to thread dump 
ruby app with ruby client

Version-Release number of selected component (if applicable):
rhc-cartridge-rack-1.1-0.85.12-1.el6_2.noarc
rhc-0.85.11-1.el6_2.noarch
Current stage


How reproducible:
Always

Steps to Reproduce:
1.Create a ruby app with rhc app create -a appstage0 -t ruby-1.8 
2.Try to thread dump it with rhc app threaddump -a appstage0
  
Actual results:
Failed to thread dump but said the application is stopped(see debug info below)

Expected results:
Thread dump ruby app successfully

Additional info:

Debug info via #rhc app threaddump -a appstage0 -d
DEBUG:
Application is stopped
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.

But actually the app is active not stopped

Comment 1 Xiaoli Tian 2012-02-03 10:06:15 UTC

Very funny that after waiting for a long time(about 2 or 3 hours), this issue does not exist any more, we could thread dump ruby app successfully now with the same steps ,not sure the reason, leave the bug open for you to check if something wrong happened in stage during this period.

Comment 2 Alex Boone 2012-02-03 12:44:15 UTC

See comments for bug 786759, I suspect these are related.  Perhaps if the app hasn't been started to allow for a thread dump, we could provide a more friendly message to the client.

Comment 3 Bill DeCoste 2012-02-03 13:13:52 UTC

Good suggestion. I'll add details for the app not being started to the error message.

Comment 4 Bill DeCoste 2012-02-03 14:06:54 UTC

added "Application is stopped. Ruby/Rack applications must be started by accessing the URL for a thread dump" message to failure.

Comment 5 Meng Bo 2012-02-06 09:44:56 UTC

verified with rhc-cartridge-rack-1.1-0.86.1-1.el6_2.noarch on devenv_1581,
addition information can be found in the output.