Create method to remove defunct MaaS alarms
Bug #1416476 reported by
Matt Thompson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Invalid
|
Medium
|
Matt Thompson | ||
Icehouse |
Won't Fix
|
Medium
|
Unassigned | ||
Juno |
Fix Released
|
Medium
|
Kevin Carter | ||
Trunk |
Invalid
|
Medium
|
Matt Thompson |
Bug Description
https:/
tags: | added: juno-backport-potential |
tags: | added: icehouse-backport-potential |
tags: | added: impacts-doc |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/151684 /git.openstack. org/cgit/ stackforge/ os-ansible- deployment/ commit/ ?id=a0e09c0da4f be009440380ad21 974cc9e5119584
Committed: https:/
Submitter: Jenkins
Branch: master
commit a0e09c0da4fbe00 9440380ad21974c c9e5119584
Author: Matt Thompson <email address hidden>
Date: Fri Jan 30 16:06:16 2015 +0000
Add functionality to nuke old checks and alarms
This commit adds some basic functionality to rpc_maas_tool.py to nuke
old alarms that should no longer exist. These include alarms containing:
WSREP_ CLUSTER_ SIZE LOCAL_STATE_ COMMENT
WSREP_
disk_free_alarm
mem_alarm
We limit deletion against alarms that also include mq_container or galera_container.
rabbit_
We also delete any checks that were created without filesystem patch defunct- checks should not be run against
included. Note that remove-
an icehouse installation as the change to check name was not backported
there.
Closes-Bug: #1416476 6a15e718516f0da b9ea2c68c27
Change-Id: I3528f5712d5a2d