Fix issue with haproxy not restarted
We are currently seeing amulet test runs fail due to keystone ports not being open. This is a result of haproxy not being restarted once its config has been setup. This patch fixes this issue by catching more cases where haproxy config can be changed. Change-Id: I1d6aa20ba0415cb8bf37b07fd1b128f20a0f8720
This commit is contained in:
parent
68a0c87235
commit
a59de539ed
|
@ -667,6 +667,7 @@ def cluster_changed():
|
|||
|
||||
|
||||
@hooks.hook('leader-elected')
|
||||
@restart_on_change(restart_map(), stopstart=True)
|
||||
def leader_elected():
|
||||
log('Unit has been elected leader.', level=DEBUG)
|
||||
# When the local unit has been elected the leader, update the cron jobs
|
||||
|
@ -677,6 +678,7 @@ def leader_elected():
|
|||
|
||||
|
||||
@hooks.hook('leader-settings-changed')
|
||||
@restart_on_change(restart_map(), stopstart=True)
|
||||
def leader_settings_changed():
|
||||
# Since minions are notified of a regime change via the
|
||||
# leader-settings-changed hook, rewrite the token flush cron job to make
|
||||
|
|
Loading…
Reference in New Issue