[
https://issues.apache.org/jira/browse/AMBARI-8511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231703#comment-14231703
]
Hadoop QA commented on AMBARI-8511:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12684678/AMBARI-8511.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 .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/791//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/791//console
This message is automatically generated.
> Alerts UI: Disabling alert-definition not updating alert-instance counts
> ------------------------------------------------------------------------
>
> Key: AMBARI-8511
> URL: https://issues.apache.org/jira/browse/AMBARI-8511
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Oleg Nechiporenko
> Assignee: Oleg Nechiporenko
> Fix For: 2.0.0
>
> Attachments: AMBARI-8511.patch
>
>
> I had an alert-definition with 1 critical instance. I then disabled the
> alert-definition and waited for the instance count to go away. However the
> definition still had 1 critical. When I refreshed the URL, the
> alert-definition correctly did not have any instances.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
