Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-3405

SSH action shows empty error Message and Error code

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 5.1.0
    • 5.2.0
    • None
    • None

    Description

      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.

      SshActionExecutor#getActionStatus
       ...
       String outFile = getRemoteFileName(context, action, "error", false, true);
       String checkErrorCmd = SSH_COMMAND_BASE + action.getTrackerUri() + " ls " + outFile;
       int retVal = getReturnValue(checkErrorCmd);
       ...
      

       
      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

      Attachments

        1. OOZIE-3405-V2.patch
          10 kB
          Mate Juhasz
        2. OOZIE-3405-V1.patch
          10 kB
          Mate Juhasz

        Issue Links

          Activity

            People

              matijhs Mate Juhasz
              orova Peter Orova
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: