[openstack-ansible][Yoga] Unable to deploy masakari on openstack-ansible
Dear Team, My masakari playbook is failing with below error: TASK [pacemaker_corosync : Creates corosync config] **************************************************************************************************** Tuesday 21 May 2024 16:24:32 +0530 (0:00:00.369) 0:00:08.576 *********** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible.errors.AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt' fatal: [bbs-p-swaas-compute1]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt'"} Below is few lines from /etc/ansible/roles/pacemaker_corosync/templates/corosync.conf.j2 {% if inventory_hostname in groups[pacemaker_corosync_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_corosync_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% elif pacemaker_remote_group in groups and inventory_hostname in groups[pacemaker_remote_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_remote_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% endif %} Regards, Danish Khan
Hey, And do you have br-mgmt interface on your bbs-p-swaas-compute1? On Tue, May 21, 2024, 14:37 Danish Khan <danish52.jmi@gmail.com> wrote:
Dear Team,
My masakari playbook is failing with below error:
TASK [pacemaker_corosync : Creates corosync config] **************************************************************************************************** Tuesday 21 May 2024 16:24:32 +0530 (0:00:00.369) 0:00:08.576 *********** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible.errors.AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt' fatal: [bbs-p-swaas-compute1]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt'"}
Below is few lines from /etc/ansible/roles/pacemaker_corosync/templates/corosync.conf.j2
{% if inventory_hostname in groups[pacemaker_corosync_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_corosync_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% elif pacemaker_remote_group in groups and inventory_hostname in groups[pacemaker_remote_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_remote_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% endif %}
Regards, Danish Khan
Yes, I have br-mgmt on all compute nodes. Masakari playbook is failing even on those nodes on which it ran successfully few months ago. Regards, Danish Khan On Tue, 21 May, 2024, 6:35 pm Dmitriy Rabotyagov, <noonedeadpunk@gmail.com> wrote:
Hey,
And do you have br-mgmt interface on your bbs-p-swaas-compute1?
On Tue, May 21, 2024, 14:37 Danish Khan <danish52.jmi@gmail.com> wrote:
Dear Team,
My masakari playbook is failing with below error:
TASK [pacemaker_corosync : Creates corosync config] **************************************************************************************************** Tuesday 21 May 2024 16:24:32 +0530 (0:00:00.369) 0:00:08.576 *********** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible.errors.AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt' fatal: [bbs-p-swaas-compute1]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt'"}
Below is few lines from /etc/ansible/roles/pacemaker_corosync/templates/corosync.conf.j2
{% if inventory_hostname in groups[pacemaker_corosync_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_corosync_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% elif pacemaker_remote_group in groups and inventory_hostname in groups[pacemaker_remote_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_remote_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% endif %}
Regards, Danish Khan
And do you have this patch [1] to the os-masakari-install included? As I actually sounds like some facts gathering issue. As I see it was backported to yoga, and is present only since version 25.3.2 [1] https://review.opendev.org/c/openstack/openstack-ansible/+/880607 On Tue, May 21, 2024, 16:15 Danish Khan <danish52.jmi@gmail.com> wrote:
Yes, I have br-mgmt on all compute nodes.
Masakari playbook is failing even on those nodes on which it ran successfully few months ago.
Regards, Danish Khan
On Tue, 21 May, 2024, 6:35 pm Dmitriy Rabotyagov, <noonedeadpunk@gmail.com> wrote:
Hey,
And do you have br-mgmt interface on your bbs-p-swaas-compute1?
On Tue, May 21, 2024, 14:37 Danish Khan <danish52.jmi@gmail.com> wrote:
Dear Team,
My masakari playbook is failing with below error:
TASK [pacemaker_corosync : Creates corosync config] **************************************************************************************************** Tuesday 21 May 2024 16:24:32 +0530 (0:00:00.369) 0:00:08.576 *********** An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ansible.errors.AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt' fatal: [bbs-p-swaas-compute1]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'br_mgmt'"}
Below is few lines from /etc/ansible/roles/pacemaker_corosync/templates/corosync.conf.j2
{% if inventory_hostname in groups[pacemaker_corosync_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_corosync_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% elif pacemaker_remote_group in groups and inventory_hostname in groups[pacemaker_remote_group] %} {% set _pacemaker_corosync_bind_addr = ansible_facts[pacemaker_remote_ring_interface | replace('-', '_')]['ipv4']['address'] %} {% endif %}
Regards, Danish Khan
participants (2)
-
Danish Khan
-
Dmitriy Rabotyagov