Comment 3 for bug 1466982

When running on a multi node environment that was already clustered the removal of this user on one node results in the remove of the user on all nodes and due to the speed at which this task is being executed there is a race condition once the user lookup has been completed. We are likely going to need to add something like "failed_when: false" to the task to simply all it to always continue regardless of the task state.

TASK: [rabbitmq_server | Ensure default rabbitmq guest user is removed] *******
changed: [aio1_rabbit_mq_container-5d9b0cfc]
failed: [aio1_rabbit_mq_container-e8e4279d] => {"cmd": "/usr/sbin/rabbitmqctl -q -n rabbit delete_user guest", "failed": true, "rc": 2}
stderr: Error: no_such_user: guest

msg: Error: no_such_user: guest
failed: [aio1_rabbit_mq_container-bb27526c] => {"cmd": "/usr/sbin/rabbitmqctl -q -n rabbit delete_user guest", "failed": true, "rc": 2}
stderr: Error: no_such_user: guest

msg: Error: no_such_user: guest

FATAL: all hosts have already failed -- aborting