Back to bug 1032554
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Eoghan Glynn | 2013-11-20 11:48:30 UTC | Priority | unspecified | high |
| Status | NEW | ASSIGNED | ||
| Target Release | --- | 4.0 | ||
| Target Milestone | --- | rc | ||
| Severity | unspecified | medium | ||
| Eoghan Glynn | 2013-11-20 11:49:22 UTC | Link ID | Launchpad 1253057 | |
| Perry Myers | 2013-11-21 14:38:43 UTC | CC | pmyers | |
| Assignee | rhos-maint | eglynn | ||
| Eoghan Glynn | 2013-11-29 13:31:57 UTC | Status | ASSIGNED | POST |
| Jakub Ruzicka | 2013-11-29 15:03:01 UTC | Status | POST | MODIFIED |
| Fixed In Version | python-ceilometerclient-1.0.7-1.el6ost | |||
| Ami Jeain | 2013-11-29 16:08:24 UTC | Keywords | OtherQA | |
| QA Contact | ajeain | kwhitney | ||
| errata-xmlrpc | 2013-12-04 21:11:27 UTC | Status | MODIFIED | ON_QA |
| Eoghan Glynn | 2013-12-09 18:07:30 UTC | Doc Text | Cause: updates to unrelated alarm attributes via the CLI caused to the repeat_actions attribute to be set to False as an unintended side-effect. Consequence: autoscaling actions stopped happening after an underpinng alarm was updated, as the cooldown logic depends on continuous notification of the alarm state. Fix: the CLI now only updates the repeat_actions attribute when explicitly requested to do so. Result: autoscaling actions continue to occur after the underpinning alarms have been updated. |
|
| Bruce Reeler | 2013-12-10 01:38:59 UTC | CC | breeler | |
| Doc Text | Cause: updates to unrelated alarm attributes via the CLI caused to the repeat_actions attribute to be set to False as an unintended side-effect. Consequence: autoscaling actions stopped happening after an underpinng alarm was updated, as the cooldown logic depends on continuous notification of the alarm state. Fix: the CLI now only updates the repeat_actions attribute when explicitly requested to do so. Result: autoscaling actions continue to occur after the underpinning alarms have been updated. | In Ceilometer, updates to unrelated alarm attributes via the CLI caused the repeat_actions attribute to be set to False as an unintended side-effect. As a result, autoscaling actions would stop if an underpinning alarm was updated. This has been fixed so that the CLI now only updates the repeat_actions attribute when explicitly requested to do so. Now, autoscaling actions continue to occur after the underpinning alarms have been updated. | ||
| Eoghan Glynn | 2013-12-11 16:54:01 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2013-12-19 17:40:46 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2013-12-20 00:37:37 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2013-12-19 19:37:37 UTC | |||
| John Skeoch | 2014-02-02 22:40:58 UTC | CC | srevivo | |
| Perry Myers | 2016-04-26 15:27:40 UTC | CC | pmyers |
Back to bug 1032554