Bug 818309

Summary:	jboss hooks (particularly configure) doesn't output anything back to the broker
Product:	OKD	Reporter:	Dan McPherson <dmcphers>
Component:	Containers	Assignee:	Dan Mace <dmace>
Status:	CLOSED UPSTREAM	QA Contact:	libra bugs <libra-bugs>
Severity:	low	Docs Contact:
Priority:	high
Version:	2.x	CC:	dmace, jhonce, mmcgrath, rmillner
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-04-16 16:37:05 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 Dan McPherson 2012-05-02 17:47:33 UTC

Description of problem:

jboss hooks (particularly configure) doesn't output anything back to the broker

Instead they redirect output to a log.  This is problematic if a failure occurs since the app is immediately destroyed.  I don't think there is a technical reason we want jboss to behave differently than the other types.  Although I know this was done originally because of output streams being left open by starting jboss.  We need to find a solution that can solve the steam being left open issue and still return the output to the caller.

Note: A simple hack might be to just cat the current log at the end.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Jhon Honce 2012-08-29 18:37:33 UTC

*** Bug 852524 has been marked as a duplicate of this bug. ***

Comment 2 Mike McGrath 2013-02-13 19:28:33 UTC

Any update here?  Will the new cartridge format fix this?

Comment 3 Jhon Honce 2013-02-14 16:54:10 UTC

This will be corrected when ported to new cartridge format.

Comment 4 Dan McPherson 2013-02-14 17:21:46 UTC

If a bug is fixed you can mark it ON_QA.  Shouldn't close a bug without it going through QE.

Comment 5 Mike McGrath 2013-04-16 16:37:05 UTC

We think this is going to be as fixed as possible.  It's not perfect but it's better than it was before as a result of some re-work with the v2 format.