[Bug 1728527] Re: hostmonitor can not monitor pacemaker_remote node via cibadmin query

[OpenStack Infra]

Reviewed:  https://review.opendev.org/647756
Committed: https://git.openstack.org/cgit/openstack/masakari-monitors/commit/?id=dc9b77772417c99368a4bbe243bb8e0e7c0bca47
Submitter: Zuul
Branch:    master

commit dc9b77772417c99368a4bbe243bb8e0e7c0bca47
Author: Liam Young <liam.young at canonical.com>
Date:   Tue Mar 19 20:05:22 2019 +0000

    Use crm_mon for pacemaker-remote deployments
    
    As described in bug #1728527 cibadmin does not expose the state of
    the pacemaker-remote nodes which means hostmonitor cannot track
    them. This change switches to use crm_mon to check the status of
    remote nodes if the new config option host.restrict_to_remotes
    to set to True. This will trigger host monitor to use crm_mon
    to monitor nodes and will only monitor nodes that are marked
    as remotes (not members).
    
    Change-Id: I3f2026805413504c875ea5f39eb036d44b26dd43
    Depends-On: Iaa2251708616e9c69817bf5b346d795ea7a4d21b
    Closes-Bug: #1728527


** Changed in: masakari-monitors
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1728527

Title:
  hostmonitor can not monitor pacemaker_remote node via cibadmin query

Status in Ubuntu Cloud Archive:
  Fix Released
Status in Ubuntu Cloud Archive rocky series:
  New
Status in Ubuntu Cloud Archive stein series:
  Fix Released
Status in masakari-monitors:
  Fix Released
Status in masakari-monitors package in Ubuntu:
  Fix Released
Status in masakari-monitors source package in Disco:
  Fix Released

Bug description:
  Currently Masakari host-monitor only grep the `crmd` status of real node via `cibadmin -Q` command.
  In case of pacemaker_remote, the `crmd` attribute is not existed, so remote node always marked in `None` state.

  Below is an example xml status of remote node:
  <node_state remote_node="true" id="cpu1" uname="cpu1" crm-debug-origin="remote_node_init_status" node_fenced="0">
        <transient_attributes id="cpu1">
          <instance_attributes id="status-cpu1"/>
        </transient_attributes>
      </node_state>
      <node_state remote_node="true" id="cpu2" uname="cpu2" crm-debug-origin="remote_node_init_status" node_fenced="0"/>

  And the log from masakari hostmonitor:
  2017-10-30 14:15:44.679 1813 INFO masakarimonitors.hostmonitor.host_handler.handle_host [-] Recognized 'cpu1' as a new member of cluster. Host status is 'None'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1728527/+subscriptions