Bug 824773 - If script returns -1, operation fails without details.
If script returns -1, operation fails without details.
Product: JBoss Operations Network
Classification: JBoss
Component: Operations (Show other bugs)
JON 3.0.1
Unspecified Unspecified
unspecified Severity low
: GA
: JON 3.2.0
Assigned To: John Mazzitelli
Mike Foley
Depends On:
  Show dependency treegraph
Reported: 2012-05-24 04:50 EDT by bkramer
Modified: 2014-01-02 15:43 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 824775 (view as bug list)
Last Closed: 2014-01-02 15:43:27 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker EMBJOPR-344 Minor Open If script returns -1, operation fails without details. Let's display stderr. 2014-06-03 13:54:11 EDT

  None (edit)
Description bkramer 2012-05-24 04:50:11 EDT
Description of problem:
If some shell script returns something else than 0, JON operation only says "Exit code was '1', see operation results for details", but there are no op results. The JON UI should not fail with this generic message.

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

How reproducible:

Steps to Reproduce:
1.run the wsprovide.sh with no arguments.
Actual results:
The operation will fail but the output of the failure icon will show the following generic message:

java.lang.Exception: Exit code was '1', see operation results for details
at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)

Expected results:
The operation should fail but the output of the failure icon should point to the proper cause of the failure. 

Additional info:
The same issue was raised for JBoss Admin console (EMBJOPR-344: https://issues.jboss.org/browse/EMBJOPR-344)
Comment 1 Mike Foley 2012-05-29 10:41:34 EDT
per BZ Triage 5/29/2012 (ccrouch, loleary, asantos, mfoley, myarborough) moving these to JON 3.1.1 or later
Comment 2 Charles Crouch 2012-09-25 15:35:28 EDT
From EMBJOPR-344 the goal would be to display the output of stderr as part of the operation results.
Comment 3 Charles Crouch 2012-09-25 15:36:38 EDT
Setting priority to medium, since this is not a high impact issue.
Comment 4 Heiko W. Rupp 2013-09-13 10:56:21 EDT
can you please investigate the effort of a fix here?
Comment 5 John Mazzitelli 2013-09-13 14:21:27 EDT
i'm working on this. should be easy to fix
Comment 6 John Mazzitelli 2013-09-13 14:36:50 EDT
git master commit : 31ec51e 

we now show the results (as defined by the plugin metadata) in the UI, even if the operation failed. This is helpful in cases like this where the results contain data that might be helpful to the user to figure out why the failure occurred.

Note You need to log in before you can comment on or make changes to this bug.