Default Masakari config fails when host monitors need to take action

Bug #1933209 reported by Radosław Piliszek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla-ansible
Fix Released
High
Radosław Piliszek
Wallaby
Fix Committed
High
Unassigned
Xena
Fix Released
High
Radosław Piliszek

Bug Description

Due to using ``restrict_to_remotes = True`` which breaks some checks (Masakari bug #1933203), Kolla Ansible has to set ``disable_ipmi_check = True`` as well. Kolla Ansible does not manage Pacemaker IPMI credentials so no functionality is lost.

Error excerpt:

File "masakarimonitors/hostmonitor/host_handler/parse_cib_xml.py", line 152, in get_stonith_ipmi_params
ERROR masakarimonitors.hostmonitor.host_handler.handle_host child_list = list(self.cib_tag)
ERROR masakarimonitors.hostmonitor.host_handler.handle_host TypeError: 'NoneType' object is not iterable

Tags: masakari
Revision history for this message
Radosław Piliszek (yoctozepto) wrote (last edit ):

The workaround (fix on kolla side) is to set:

  [host]
  disable_ipmi_check = True

in {{ node_custom_config }}/masakari/masakari-hostmonitor.conf
(where {{ node_custom_config }} is /etc/kolla by default)
and rerun ``kolla-ansible deploy``.

description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (master)
Changed in kolla-ansible:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (master)

Reviewed: https://review.opendev.org/c/openstack/kolla-ansible/+/799110
Committed: https://opendev.org/openstack/kolla-ansible/commit/f71646da186f74fa6f562d4fbc1910ede3120a90
Submitter: "Zuul (22348)"
Branch: master

commit f71646da186f74fa6f562d4fbc1910ede3120a90
Author: Radosław Piliszek <email address hidden>
Date: Thu Jul 1 18:19:56 2021 +0000

    Fix Masakari host monitor default config

    Closes-Bug: #1933209
    Change-Id: I644ad475ca88aac0c22b14163d33a30193fe706a

Changed in kolla-ansible:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla-ansible (stable/wallaby)

Fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/kolla-ansible/+/801595

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla-ansible (stable/wallaby)

Reviewed: https://review.opendev.org/c/openstack/kolla-ansible/+/801595
Committed: https://opendev.org/openstack/kolla-ansible/commit/38748d2aae8018241455f1c329d76a8f042b1965
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit 38748d2aae8018241455f1c329d76a8f042b1965
Author: Radosław Piliszek <email address hidden>
Date: Thu Jul 1 18:19:56 2021 +0000

    Fix Masakari host monitor default config

    Closes-Bug: #1933209
    Change-Id: I644ad475ca88aac0c22b14163d33a30193fe706a
    (cherry picked from commit f71646da186f74fa6f562d4fbc1910ede3120a90)

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 12.1.0

This issue was fixed in the openstack/kolla-ansible 12.1.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla-ansible 13.0.0.0rc1

This issue was fixed in the openstack/kolla-ansible 13.0.0.0rc1 release candidate.

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.