cfn-hup triggers post.update events every time it's called
Bug #1133049 reported by
Steve Baker
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
heat-cfntools |
Triaged
|
Medium
|
Ethan Lynn |
Bug Description
From https:/
> cfn-hup currently triggers the post.update events every time it's called -- even when the metadata didn't change.
Need to fix this so we only trigger updates when the metadata has changed
Changed in heat-cfntools: | |
importance: | Undecided → High |
assignee: | Steve Baker (steve-stevebaker) → Steven Hardy (shardy) |
Changed in heat-cfntools: | |
milestone: | v1.2.1 → none |
Changed in heat-cfntools: | |
milestone: | none → v1.3.0 |
Changed in heat-cfntools: | |
milestone: | v1.2.3 → none |
Changed in heat-cfntools: | |
milestone: | none → v1.2.8 |
importance: | High → Medium |
Changed in heat-cfntools: | |
milestone: | v1.2.8 → v1.2.9 |
Changed in heat-cfntools: | |
milestone: | v1.3.0 → none |
status: | In Progress → Triaged |
To post a comment you must log in.
As I understand, the issue appears when there is more than one resource monitored by cfn-hup hooks. heat-cfntools/ last_metadata heat-cfntools/ last_metadata heat-cfntools/ last_metadata <<< different since it contains metadata of resource #1 heat-cfntools/ last_metadata
The cfn-hup workflow is something like this:
- process hook #1
- retrieve metadata of resource #1
- compare with /var/cache/
- run hook
- store metadata of resource #1 in /var/cache/
- process hook #2
- retrieve metadata of resource #2
- compare with /var/cache/
- run hook
- store metadata of resource #2 in /var/cache/