[
https://issues.apache.org/jira/browse/OOZIE-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924366#comment-16924366
]
Julia Kinga Marton edited comment on OOZIE-3405 at 9/6/19 4:16 PM:
-------------------------------------------------------------------
[~matijhs], I can see in the review that you have uploaded multiple patches.
Can you please upload your patch here as well, to trigger the precommit script,
or this one is the last one?
was (Author: kmarton):
[~matijhs], I can see in the review that you have uploaded multiple patches.
Can you please upload your patch here as well, to trigger the precommit script?
> SSH action shows empty error Message and Error code
> ---------------------------------------------------
>
> Key: OOZIE-3405
> URL: https://issues.apache.org/jira/browse/OOZIE-3405
> Project: Oozie
> Issue Type: Improvement
> Affects Versions: 5.1.0
> Reporter: Peter Orova
> Assignee: Mate Juhasz
> Priority: Minor
> Fix For: trunk
>
> Attachments: OOZIE-3405-V1.patch
>
>
> Currently, when an SSH action fails the only message that is returned is the
> Status. Neither the {{error Message}} nor {{Error code}} fields are filled.
> This makes reporting on the causes of SSH Action failures via Oozie highly
> impractical: the only meaningful bit of information there is on a failed SSH
> Action is the Status.
> The Status is filled based on the presence (or lack of) the {{.error file}}
> that is produced in case the user submitted script returns with any other
> value than 0.
> {noformat}
> SshActionExecutor#getActionStatus
> ...
> String outFile = getRemoteFileName(context, action, "error", false, true);
> String checkErrorCmd = SSH_COMMAND_BASE + action.getTrackerUri() + " ls " +
> outFile;
> int retVal = getReturnValue(checkErrorCmd);
> ...
> {noformat}
>
> User requirement is to provide some more detailed information on the
> success/failure of the user-submitted script. That could be at a minimum the
> return value, optionally the last ~1K of the stderr that is drained. This
> information could then be communicated via {{errorMessage}} and {{ErrorCode}}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)