alanbover / deathnode

85%

master: 85%

LAST BUILD ON BRANCH fix_refresh_lifecyclehook_issue

branch: fix_refresh_lifecyclehook_issue

CHANGE BRANCH

x

Reset

• fix_refresh_lifecyclehook_issue
• add_lifecycle_timeout_reset
• code_refactor
• enable_travis_and_improve_doc
• filter_protected_instances
• filterframeworkcontraint
• fix_crash_when_no_instance_found
• improve_code_reports
• make_deathnode_tag_configurable
• master
• move_tests_to_convey
• recover_untracked_terminating_instances
• revert-32-code_refactor
• some_refactor
• tasklabels
• use_lifecycles

Fix issue with refreshlifecycle hooks

When deathnode is restarted, it recreates the state reading from AWS.
For those instances already terminating, it was re-tagging it with a new
epoch time without reseting the lifecycle timeout, which allowed the possibility
for the timeout to expire without deathnode triggering the refresh.