WatchRule initial state should be NODATA not NORMAL
Bug #1102446 reported by
Steven Hardy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Heat |
Fix Released
|
Medium
|
Steven Hardy | ||
| Grizzly |
Fix Released
|
Medium
|
Steven Hardy | ||
Bug Description
According to AWS CloudWatch documentation, Alarm state after initial creation is set to INSUFFICIENT_DATA, but we currently set it to OK without doing any evaluation of the rule.
We should set the rule to NODATA, then the transition from the inital NODATA state to NORMAL (OK) can be detected correctly (e.g so OKActions can be correctly interpreted for AWS::CloudWatch
http://
http://
| Changed in heat: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| assignee: | nobody → Steven Hardy (shardy) |
| milestone: | none → grizzly-3 |
| Changed in heat: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to heat (master) | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to heat (master) | #2 |
| Changed in heat: | |
| status: | In Progress → Fix Committed |
| Changed in heat: | |
| status: | Fix Committed → Fix Released |
| Changed in heat: | |
| milestone: | grizzly-3 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/