Upstream Spring issue blocks RabbitMQ 4.3 upgrade

[cailyoung]

RabbitMQ 4.3 is the only one in support at the moment. When upgrading, we see this with the api pod crashing:

<snip>
api Caused by: com.rabbitmq.client.ShutdownSignalException: connection error; protocol method: #method<connection.close>(reply-code=541, reply-text=INTERNAL_ERROR - Feature `queue_master_locator` is deprecated.
api By default, this feature is not permitted anymore.
api The feature will be removed from a future major RabbitMQ version, regardless of the configuration; actual version to be determined.
api To con..., class-id=50, method-id=10)
api     at com.rabbitmq.utility.ValueOrException.getValue(ValueOrException.java:66)
api     at com.rabbitmq.utility.BlockingValueOrException.uninterruptibleGetValue(BlockingValueOrException.java:36)
api     at com.rabbitmq.client.impl.AMQChannel$BlockingRpcContinuation.getReply(AMQChannel.java:552)
api     at com.rabbitmq.client.impl.AMQChannel.privateRpc(AMQChannel.java:316)
api     at com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:152)
api     ... 79 common frames omitted
api 
stream closed: EOF for reportportal/reportportal-api-665f4bcc57-5v74m (api)

spring-projects/spring-amqp#3419

Looks like it's been backported, you may want to document the workaround:

deprecated_features.permit.queue_master_locator = true

[Pink-Bumblebee]

Hello @cailyoung , thank you for highlight and for workaround.
I suspect that this issue with Rabbit happens when users will try to use Rabbit 4.3.(X) (latest version is 4.3.0 for the date, when this comment published). For version 4.2.6 looks like everything is Ok.
Just 2 screenshots with Deprecated Features statuses in different versions of Rabbit: