[AMBARI-8430] Current Alerts Should Be Cleaned Up With Ambari Cluster/Service/Component/Host Changes

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: alerts, ambari-server
• Epic Link: Alerts Redesign
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 24/Nov/14 17:38
• Updated: 25/Nov/14 22:51
• Resolved: 25/Nov/14 21:58

Description

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.

Issue Links

• links to: Reviewboard