Back to bug 1398339
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Mehdi ABAAKOUK | 2016-11-24 13:35:22 UTC | Link ID | OpenStack gerrit 402027 | |
| Mehdi ABAAKOUK | 2016-11-24 13:35:42 UTC | Link ID | Launchpad 1644550 | |
| Mehdi ABAAKOUK | 2016-11-24 13:35:52 UTC | Status | NEW | ON_DEV |
| Mehdi ABAAKOUK | 2016-11-24 14:00:12 UTC | Status | ON_DEV | NEW |
| Link ID | OpenStack gerrit 402027 Launchpad 1644550 | |||
| Franck Baudin | 2016-11-25 14:20:00 UTC | Keywords | Triaged | |
| CC | fbaudin | |||
| Mehdi ABAAKOUK | 2016-11-28 12:26:03 UTC | Status | NEW | ASSIGNED |
| Mehdi ABAAKOUK | 2016-11-28 14:44:30 UTC | Link ID | OpenStack gerrit 403739 | |
| Mehdi ABAAKOUK | 2016-11-28 14:45:45 UTC | Link ID | Launchpad 1645344 | |
| RHEL Program Management | 2016-12-01 13:26:50 UTC | Keywords | ZStream | |
| Pradeep Kilambi | 2017-01-11 13:36:18 UTC | Status | ASSIGNED | POST |
| Jon Schlueter | 2017-01-12 12:36:52 UTC | Link ID | OpenStack gerrit 403739 | OpenStack gerrit 417374 |
| Pradeep Kilambi | 2017-01-27 15:43:21 UTC | QA Contact | yprokule | ssmolyak |
| Jon Schlueter | 2017-02-14 17:44:24 UTC | Target Milestone | --- | z2 |
| Jon Schlueter | 2017-02-14 17:48:51 UTC | Status | POST | MODIFIED |
| Fixed In Version | openstack-aodh-3.0.1-6.el7ost | |||
| errata-xmlrpc | 2017-02-14 19:40:07 UTC | Status | MODIFIED | ON_QA |
| Martin Lopes | 2017-02-17 02:49:16 UTC | CC | mlopes | |
| Flags | needinfo?(jschluet) | |||
| Mehdi ABAAKOUK | 2017-02-17 10:28:12 UTC | Link ID | OpenStack gerrit 435347 | |
| Doc Text | Cause: Aodh composite alarm was not computing the final alarm state correctly, when one alarm that compose it have only a trending state and not hard state. Trending state occurs only when the alarm monitor new data, usually just after an alarm is created or the resource that the alarm monitor is created. Consequence: Aodh composite alarm can report a wrong state at the beginning of alarm life. Fix: Update package to openstack-aodh-3.0.1-6.el7ost Result: Aodh composite alarm doesn't report wrong state anymore. | |||
| Doc Type | If docs needed, set a value | Bug Fix | ||
| Flags | needinfo?(jschluet) | |||
| Martin Lopes | 2017-02-20 06:37:26 UTC | Doc Text | Cause: Aodh composite alarm was not computing the final alarm state correctly, when one alarm that compose it have only a trending state and not hard state. Trending state occurs only when the alarm monitor new data, usually just after an alarm is created or the resource that the alarm monitor is created. Consequence: Aodh composite alarm can report a wrong state at the beginning of alarm life. Fix: Update package to openstack-aodh-3.0.1-6.el7ost Result: Aodh composite alarm doesn't report wrong state anymore. | Prior to this update, the aodh composite alarm would not compute the final alarm state correctly. This occurred when one alarm only had a trending state and not a hard state. The trending state occurrs only when the alarm monitors new data, which is usually just after an alarm is created, or when the resource that the alarm monitors is created. Consequently, the aodh composite alarm would report the incorrect state at the beginning of the alarm life. With this update, the aodh has been updated to openstack-aodh-3.0.1-6.el7ost. As a result, the aodh composite alarm no longer reports the incorrect state. |
| nlevinki | 2017-02-28 13:50:14 UTC | Status | ON_QA | VERIFIED |
| CC | nlevinki | |||
| errata-xmlrpc | 2017-03-01 00:16:25 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2017-03-01 13:38:14 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-03-01 08:38:14 UTC |
Back to bug 1398339