[ 
https://issues.apache.org/jira/browse/AMBARI-19298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778651#comment-15778651
 ] 

Hadoop QA commented on AMBARI-19298:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12844694/AMBARI-19298.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in 
ambari-server.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9823//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/9823//console

This message is automatically generated.

> If Oozie load balancer is stopped the error is not informative
> --------------------------------------------------------------
>
>                 Key: AMBARI-19298
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19298
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Andrew Onischuk
>            Assignee: Andrew Onischuk
>             Fix For: 3.0.0
>
>         Attachments: AMBARI-19298.patch
>
>
> During uploading sharelib any exception are hidden by this informative
> message:
>     
>     Code is non-zero or output is empty. Code: 1
> So I had to debug the code. Just to later discover that load balancer was just
> not running and being the reason for failure.  
> We have to come up with something more informative in case our users hit this
> due to misconfiguration of load balancer or due to any other error causing 
> sharelib upload to fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to