Bug 839901

Summary: Inccorect thread dump file path is provided after generating thead dump for jbosseap app
Product: OKD Reporter: joycezhang <jinzhang>
Component: ocAssignee: Bill DeCoste <wdecoste>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.xCC: jhonce, rmillner, xtian
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 20:42:35 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 joycezhang 2012-07-13 07:39:21 UTC 
Description of problem:
Inccorect thread dump file path is provided after generating thread dump file for jbosseap-6.0. Following error is displayed if using the provided path:

# rhc app tail -a jbooeap -f jbooeap/jbossas-7/standalone/tmp/jbooeap.log -o '-n 250'
Password: ******

Attempting to tail files: jbooeap/jbossas-7/standalone/tmp/jbooeap.log
Use ctl + c to stop
Could not find any files matching glob



[root@Joycezh jbooeap]# 

Version-Release number of selected component (if applicable):
rhc-0.95.13
stg.openshift.redhat.com
Fedora17

How reproducible:
always

Steps to Reproduce:
1. Create an app with the type jbosseap-6.0
#rhc app create -a jbooeap -t jbosseap-6.0 -l test -p **
2. Generate thread dump file
# rhc app threaddump -a jbooeap -l test -p **
3. Check the generated log file with the provided path:
The thread dump file will be available via: rhc app tail -a jbooeap -f jbooeap/jbossas-7/standalone/tmp/jbooeap.log -o '-n 250'
  
Actual results:
The provided path is incorrect as it could not find any files matching glob.

Expected results:
The generated log file can be displayed with the path.

Additional info:
# rhc app tail -a jbooeap -f jbosseap-6.0/jbosseap-6.0/standalone/tmp/jbooeap.log -o '-n 250'
Comment 1 Jhon Honce 2012-07-14 01:17:11 UTC 
Fix in https://github.com/openshift/crankcase/pull/236
Comment 2 Jhon Honce 2012-07-14 17:57:49 UTC 
li commit 308d48e45c655ae088e1b70aa118baf1c2ac7daf
Comment 3 Bill DeCoste 2012-07-14 18:18:36 UTC 
Fixed in master
Comment 4 joycezhang 2012-07-17 05:23:59 UTC 
Verified build:
rhc-0.95.14
devenv_1885

Verified results:
The correct path is provided when generating thread dump file, Please refer to following message copied from command line.
#rhc app threaddump -a app1 -p redhat

RESULT:
Success

The thread dump file will be available via: rhc app tail -a app1 -f app1/jbosseap-6.0/standalone/tmp/app1.log -o '-n 250'


So it is fixed and can be closed.  Thanks.
Comment 5 joycezhang 2012-07-17 05:26:57 UTC 
It fixed with devenv_1895, not devenv_1885. Thanks.