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

Hadoop QA commented on AMBARI-9868:
-----------------------------------

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

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

This message is automatically generated.

> No feedback is shown for bulk start/stop operations if the target host 
> components are already started/stopped
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-9868
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9868
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-9868.patch
>
>
> This is a result of the fix done in.  In case the server returns 200 on bulk 
> start/stop, we need to let the user know that there was nothing to do (we can 
> show the same "Nothing to do" popup - see); otherwise it seems like the 
> request failed silently.



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

Reply via email to