Since RabbitMQ 3.7.4, the CLI tools (rabbitmqctl and friends)
parallelize the querying of information from cluster members. In
order to receive stream data back, the cli instance binds and
registers itself on an available port (default between 35672 and
35682, inclusive). If these ports are firewalled off, then
rabbitmqctl commands such as list_queues will hang waiting for data
from remote cluster members.
This patch does two things:
1) Reconfigures rabbitmqctl to bind to 25673-25683 instead of the
default range of 35672-35682. This ensures the ports are not in the
ephemeral port range and avoids unintended collisions.
2) Opens the firewall on 25673-25683 to enable communication.
Resolves: rhbz#1811680
Change-Id: If5caa51cd9a3aef97d06d491dde1d5129cc1a569
(cherry picked from commit a2bc2e10b0)
(cherry picked from commit 40a1e5ba18)
e80356e454