To Reproduce Steps to reproduce the behavior:

1. Try overcloud deploy with more than 900 nodes

Expected behavior

• overcloud deploy command succeeds

Bug impact

• By this issue, every overcloud deploy cannot complete without the modification to puppet-rabbitmq.

Known workaround

• Increase timeout value to 20 in /usr/share/openstack-puppet/modules/rabbitmq/lib/puppet/provider/rabbitmq_cli.rb

def self.run_with_retries(count = 30, step = 6, timeout = 10)

Additional information
In the deployment, `rabbitmqctl -q status` took more than 10 seconds.

# time rabbitmqctl -q status
...
real    0m12.200s
user    0m0.490s
sys     0m0.263s

Due to that, rabbitmq_policy function which uses rabbitmqctl command always failed by timeout.
It looks that scalability issue and we need to make timeout configurable.