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

James Page james.page at ubuntu.com
Fri Apr 12 06:48:37 UTC 2019


This bug was fixed in the package masakari-monitors - 7.0.0~rc1-0ubuntu2~cloud0
---------------

 masakari-monitors (7.0.0~rc1-0ubuntu2~cloud0) bionic-stein; urgency=medium
 .
   * New update for the Ubuntu Cloud Archive.
 .
 masakari-monitors (7.0.0~rc1-0ubuntu2) disco; urgency=medium
 .
   [ Corey Bryant ]
   * d/control: Set source package Section to net, fixing
     binary-control-field-duplicates-source lintian tag.
 .
   [ James Page ]
   * d/p/bug1728527.patch: Cherry pick fix to resolve issues with use of
     pacemaker-remote for remote management of hypervisors (LP: #1728527).


** Changed in: cloud-archive
       Status: Fix Committed => 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:
  In Progress
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



More information about the Ubuntu-openstack-bugs mailing list