[Bug 1728527] Change abandoned on masakari-monitors (master)

[OpenStack Infra]

Change abandoned by "Sei Sano <sei.sano at ntt.com>" on branch: master
Review: https://review.opendev.org/c/openstack/masakari-monitors/+/516577
Reason: This proposed change aimed to use crm_mon instead of cibadmin
to handle cases where CIB could not retrieve the remote node state.

However, the current Masakari implementation already uses crm_mon
when necessary, so this change is no longer needed.

Therefore, I'm abandoning this patch.
Please feel free to restore it if you’d like to continue the work.

-- 
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:
  Won't Fix
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