@@ -1084,25 +1084,6 @@ this_node_first(Nodes) ->
10841084
10851085rpc_call (Node , Module , Function , Args , Timeout ) ->
10861086 case rpc :call (Node , Module , Function , Args , Timeout ) of
1087- {badrpc , {'EXIT' ,
1088- {undef ,
1089- [{rabbit_feature_flags , Function , Args , []}
1090- | _ ]}}} ->
1091- % % If rabbit_feature_flags:Function() is undefined
1092- % % on the remote node, we consider it to be a 3.7.x
1093- % % pre-feature-flags node.
1094- % %
1095- % % Theoretically, it could be an older version (3.6.x and
1096- % % older). But the RabbitMQ version consistency check
1097- % % (rabbit_misc:version_minor_equivalent/2) called from
1098- % % rabbit_mnesia:check_rabbit_consistency/2 already blocked
1099- % % this situation from happening before we reach this point.
1100- ? LOG_DEBUG (
1101- " Feature flags: ~ts :~ts~tp unavailable on node `~ts `: "
1102- " assuming it is a RabbitMQ 3.7.x pre-feature-flags node" ,
1103- [Module , Function , Args , Node ],
1104- #{domain => ? RMQLOG_DOMAIN_FEAT_FLAGS }),
1105- {error , pre_feature_flags_rabbitmq };
11061087 {badrpc , Reason } = Error ->
11071088 ? LOG_ERROR (
11081089 " Feature flags: error while running:~n "
0 commit comments