Error isolating rabbitmq host

Bug #2064550 reported by howon park
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
New
Undecided
Unassigned

Bug Description

An error occurred when deploying the controller server and the rabbitmq server separately.

TASK [service-rabbitmq : nova | Ensure RabbitMQ users exist] ***********************************************************************************************************************
<RabbitMQ1> rc=0, stdout and stderr censored due to no log
FAILED - RETRYING: [Controller1 -> RabbitMQ1]: nova | Ensure RabbitMQ users exist (4 retries left).Result was: {
    "attempts": 2,
    "censored": "the output has been hidden due to the fact that 'no_log: true' was specified for this result",
    "changed": false,
    "retries": 6
}

It is identified as an error occurring in the Rabbitmq user check.
The account that needs to be found on the RabbitMQ server is being searched for on the controller server, which is causing an error.

node: "rabbit@{{ ansible_facts.hostname }}"

It seems that the patch is affecting due to the issue described in https://bugs.launchpad.net/kolla-ansible/+bug/1946506 Was the patch not considering the separation of the RabbitMQ server? We need a proper fix for this.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.