[ClusterLabs] 'expected' node attribute missing

[Ken Gaillot]

On Mon, 2017-10-30 at 10:48 +0600, Sergey Korobitsin wrote:
> Ken Gaillot ☫ → To Cluster Labs - All topics related to open-source
> clustering welcomed @ Fri, Oct 27, 2017 10:38 -0500
> 
> > > Hello,
> > > I'm trying to use https://github.com/marcan/pacemaker-exporter,
> > > and it wants 'expected' node attribute from my crm_mon -X output,
> > > but it's missing. Is that because I'm using no-quorum-
> > > policy=ignore?
> > 
> > Quorum policy won't affect it.
> > 
> > I assume you mean "expected_up" from "crm_mon -X", which I see in
> > the
> > source above. That's been part of the output since "-X" was added,
> > so
> > I'm not sure why you wouldn't have it.
> 
> I mean this piece of code:
> 
> https://github.com/marcan/pacemaker-exporter/blob/7fc2a2e0d0bfa704e68
> bd4e95d9bb84b3bfcf35d/prometheus-pacemaker-exporter.py#L95
> 
> It's literally 'expected', and 'expected_up' is the other one.

Ah, it's looking for "crm_mon -X" output like this:

  <attribute name="connected" value="1" expected="1" />

That is only set for attributes created by the ocf:pacemaker:ping
resource agent. No other node attributes will have it. Hopefully, the
exporter is not requiring that it be present for all node attributes.

Also, the XML output for node attributes was first added in Pacemaker
1.1.14, so make sure you have that or later.

> > For each node in your cluster, you should see a "<node>" entry in
> > "crm_mon -X" output, and it should include "expected_up=true" or
> > "expected_up=false".
> 
> 
-- 
Ken Gaillot <kgaillot at redhat.com>