tree d7a87821afddf80b2b18ae9759f1c335ae2e86b5
parent 7ee465f1ad1ecdc3685d152ba9f71110b8e06c09
author Willy Tarreau <w@1wt.eu> 1534832546 +0200
committer Willy Tarreau <w@1wt.eu> 1534832965 +0200
encoding latin1

BUG/MEDIUM: server: update our local state before propagating changes

Commit 3ff577e ("MAJOR: server: make server state changes synchronous again")
reintroduced synchronous server state changes. However, during the previous
change from synchronous to asynchronous, the server state propagation was
placed at the end of the function to ease the code changes, and the commit
above didn't put it back at its place. This has resulted in propagated
states to be incomplete. For example, making a server leave maintenance
would make it up but would leave its tracking servers down because they
see their tracked server is still down.

Let's just move the status update right to its place. It also adds the
benefit of reporting state changes in the order they appear and not in
reverse.

No backport is needed.