[
https://issues.apache.org/jira/browse/AMBARI-11775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14576567#comment-14576567
]
Hadoop QA commented on AMBARI-11775:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12738284/AMBARI-11775.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{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/3092//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3092//console
This message is automatically generated.
> Threading Can Cause Aggregate Alerts To Have Duplicate Alert Entries With
> Different States
> ------------------------------------------------------------------------------------------
>
> Key: AMBARI-11775
> URL: https://issues.apache.org/jira/browse/AMBARI-11775
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11775.patch
>
>
> STR:
> - install Ambari 1.7 with default services on stack 2.0
> - upgrade Ambari to version 2.0
> - stop all
> - start all
> On alerts tab there are two statuses for some of the aggregate alerts. This
> seems to be a threading issue with asynchronous events fired for the
> aggregate alerts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
