[
https://issues.apache.org/jira/browse/AMBARI-8430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225155#comment-14225155
]
Hadoop QA commented on AMBARI-8430:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12683615/AMBARI-8430.patch.2
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 13 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/750//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/750//console
This message is automatically generated.
> Current Alerts Should Be Cleaned Up With Ambari
> Cluster/Service/Component/Host Changes
> --------------------------------------------------------------------------------------
>
> Key: AMBARI-8430
> URL: https://issues.apache.org/jira/browse/AMBARI-8430
> Project: Ambari
> Issue Type: Bug
> Components: alerts, ambari-server
> Affects Versions: 2.0.0
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-8430.patch.2
>
>
> When an active alert definition is disabled, instances of that alert
> definition should not show up when query the cluster/service/host for alerts.
> STR:
> 1) Cause an alert to trigger (shut something down)
> 2) Disable the alert definition for that alert
> 3) CRITICAL alert stays in the list of current cluster alerts
> Expected: The API should prevent disabled alerts from being returned.
> Beyond this, the API should also clean up current alerts that are no longer
> valid. This includes:
> 1) Alerts that are for hosts which no longer exist
> 2) Alerts that are for a component that is no longer installed on a host
> 3) Alerts for services that are no longer part of the cluster (including the
> default group for that service)
> Alerts that are being received should also be verified for validity so that
> an invalid alert that was cached by the agent doesn't re-appear.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
