-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(bridge_v2_api): avoid calling nodes that do not support minimum bpapi #12472
fix(bridge_v2_api): avoid calling nodes that do not support minimum bpapi #12472
Conversation
f96bb6d
to
1cf08d7
Compare
1cf08d7
to
76d242d
Compare
@@ -1477,7 +1476,7 @@ t_cluster_later_join_metrics(Config) -> | |||
?assertMatch( | |||
{ok, 200, #{ | |||
<<"metrics">> := #{<<"success">> := _}, | |||
<<"node_metrics">> := [#{<<"metrics">> := #{}}, #{<<"metrics">> := #{}} | _] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Returns a single node result now, because BPAPI might not be ready / not have announced the new node's APIs yet, and thus is rejected when choosing the nodes.
I think these read operations might not be too affected by sieving the node list: when the rolling upgrade finishes, the whole information will be returned. |
[cluster, actions], | ||
[cluster, sources] | ||
]; | ||
t_older_version_nodes_in_cluster(Config) -> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this testcase going to be relevant in the future releases? If not, perhaps a manual one-off test is enough?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this still might be relevant for any rolling upgrade scenario.
Fixes https://emqx.atlassian.net/browse/EMQX-11834
Release version: v/e5.6
Summary
PR Checklist
Please convert it to a draft if any of the following conditions are not met. Reviewers may skip over until all the items are checked:
changes/(ce|ee)/(feat|perf|fix|breaking)-<PR-id>.en.md
filesChecklist for CI (.github/workflows) changes
changes/
dir for user-facing artifacts update