Alaram histories are never removed from aodh database
Bug #1891888 reported by
Takashi Kajinami
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Undecided
|
Takashi Kajinami |
Bug Description
In Aodh, alarm histories are not automatically removed and we need the following 2 configurations to have old alarm histories removed from database
1. alarm_history_
2. aodh-expirer command is executed periodically
Note that the similar expiration for Panko was previously introduced as a fix for another bug[1], and we should implement the same for aodh.
Changed in tripleo: | |
assignee: | nobody → Takashi Kajinami (kajinamit) |
status: | New → In Progress |
description: | updated |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/746424 /git.openstack. org/cgit/ openstack/ puppet- tripleo/ commit/ ?id=dadf19c6e3b 8525b45c0350c81 f3d8af14bfaa8c
Committed: https:/
Submitter: Zuul
Branch: master
commit dadf19c6e3b8525 b45c0350c81f3d8 af14bfaa8c
Author: Takashi Kajinami <email address hidden>
Date: Mon Aug 17 08:39:48 2020 +0900
Add support for aodh-expirer cron job
Related-Bug: #1891888 /review. opendev. org/#/c/ 746241/ edaa9744478d699 ccc5243b784
Depends-on: https:/
Change-Id: I9bc8a4ffde6e24