I suspect that during any stack-update where docker-puppet.py reruns for rabbitmq we are running "rabbitmqctl -q list_users", the problem is just usually not seen since rabbitmq had been previously started.
I suspect that during any stack-update where docker-puppet.py reruns for rabbitmq we are running "rabbitmqctl -q list_users", the problem is just usually not seen since rabbitmq had been previously started.