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

Hadoop QA commented on AMBARI-14207:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12775715/AMBARI-14207.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-web.

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

This message is automatically generated.

> Web Client Does Not Display Errors When Creating Upgrade
> --------------------------------------------------------
>
>                 Key: AMBARI-14207
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14207
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.2.0
>            Reporter: Xi Wang
>            Assignee: Xi Wang
>            Priority: Critical
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-14207.patch, popup.png
>
>
> When creating an upgrade, an HTTP error returned (such as a 500 error) is 
> never propagated up to the end user. 
> STR:
> - Setup a 4-host cluster with ZK, Yarn, HDFS
> - Install clients only on the 4th host
> - Place the 4th host into maintenance mode
> - Start an upgrade
> The server will correctly throw an exception since service checks cannot be 
> scheduled since 4th host in maintenance mode is excluded. The error is 
> propagated up as an HTTP 500 error:
> {code:title=HTTP/500}
> While building a service check command for YARN, there were no healthy 
> eligible hosts: unhealthy[], maintenance[c6404.ambari.apache.org]
> {code}
> This message should be shown to the end user. Otherwise, nothing happens in 
> the UI and there is no indication of an error.



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

Reply via email to