You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rabbit_feature_flags: Improve error reporting from compat. check
[Why]
So far, no matter what the error was, and no matter if it was an actual
incompatibility or something unrelated like a timeout or an Erlang
distribution failure, the `check_node_compatibility_task()` function
always logged and reported the same "nodes are incompatible" message.
This makes it unclear what is wrong. Are my two RabbitMQ nodes really
incompatible? Or was there a network issue?
[How]
Now, the function logs a more precise message explaining the source of
the error. It will also return two different return errors:
* `incompatible_feature_flags` for an actual incompatibility
* `aborted_feature_flags_compat_check`, plus the error term, for any
error not coming from the Feature flags subsystem itself.
In the end, regardless of the error, the nodes will still be considered
incompatible and possibly one of them will refuse to start. But now, the
user should better understand why.
Reported-by: @dcorbacho
0 commit comments