Hello Thamanna, Pacemaker has changed CIB format slightly in v2.1.7, hence Masakari hostmonitor does not pick up the status properly. Please see links below. https://review.opendev.org/c/openstack/masakari-monitors/+/922336 https://review.opendev.org/c/openstack/masakari-monitors/+/937638 On Sun, 2025-12-21 at 20:34 +0530, Thamanna Farhath wrote:

Hello OpenStack community, I am testing Masakari host failure recovery on OpenStack 2023.1 (Antelope) deployed using Kolla-Ansible. Environment: * 3 nodes * Each node runs controller + compute * Pacemaker + Corosync deployed on all 3 nodes * Masakari enabled (hostmonitor, instancemonitor, engine, api) * pacemaker-remote not used (all nodes are full Pacemaker members) * Masakari segment: service_type = COMPUTE recovery_method = auto Tests performed: * Process-level failures (qemu, libvirt) → detected correctly * nova-compute stop → detected (no evacuation, expected) * Host failure test: Powered off one compute/controller node Also tested systemctl stop corosync Issue: * Pacemaker shows the node as OFFLINE * However: No Masakari HOST_DOWN notification is generated No evacuation is triggered masakari-hostmonitor logs do not show host failure handling Question: In a 3-node controller+compute Pacemaker cluster, is Masakari expected to detect host failure directly from Pacemaker membership events without pacemaker-remote? Are there any additional requirements needed for Masakari host failure detection in this topology? Any guidance or references would be greatly appreciated.

Disclaimer :  The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.   E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."