[Debian-ha-maintainers] ERROR: pengine:metadata: got no meta-data, does this RA exist?

[Ferenc Wágner]

Juha Heinanen <jh at tutpro.com> writes:

> I built pacemaker 1.1.14 on Debian Jessie from Stretch source.  Built
> succeeded after some changes in debian/rules and control:
>
> override_dh_strip:
> #	dh_strip --ddeb-migration='pacemaker-dbg (<< 1.1.14~rc4-1~)'
> 	dh_strip --dbg-package=pacemaker-dbg

Unfortunately, by using pacemaker-dbg > 1.1.14~rc4 you invalidate the
ddeb-migration path used in sid/stretch.  This will lead to breakage
during upgrade if you have pacemaker-dbg installed.  And pacemaker-dbg
is a nasty package anyway, because it (originally) depends on both
pacemaker and pacemaker-remote, which break each other.  Take care.

> and downgraded pacemaker-cli-utils init-system-helpers >= 1.23
> dependency since it would have required whole init system upgrade:

There was a reason for this requirement:

>  # ... because << 1.23 starts our disabled crm_mon service on install and
> # upgrade, see #768456.

But you can easily install 1.23 or 1.24 from snapshots.d.o into a jessie
system.

> After building the packages and installing them on my existing pacemaker
> host, all services came up without problems.

Cool.

> I then erased existing crm config and tried to create a new one from
> scratch.  It, however, failed complaining that the RA does not exist.
> For example:
>
> # crm configure
> crm(live)configure# primitive virtual-ip ocf:heartbeat:IPaddr2 params ip=192.98.103.40 broadcast=192.98.103.255 cidr_netmask=24 op monitor interval=15s
> crm(live)configure# There are changes pending. Do you want to commit them (y/n)? y
> ERROR: error: unpack_resources:	Resource start-up disabled since no STONITH resources have been defined
>    error: unpack_resources:	Either configure some or disable STONITH with the stonith-enabled option
>    error: unpack_resources:	NOTE: Clusters with shared data need STONITH to ensure data integrity
> Errors found during check: config not valid
> ERROR: pengine:metadata: got no meta-data, does this RA exist?
>
> That is, I experienced the same what Arturo had reported in Bug#815823.
>
> Any ideas what might be going wrong are appreciated.

There are known incompatibilities between current pacemaker and crmsh.
Does it help if you create the symlink /usr/lib/pacemaker ->
/usr/lib/x86_64-linux-gnu/pacemaker?  That could help crmsh find some
pacemaker components.  Don't forget to remove that symlink after
testing, because the pending pacemaker package will use that directory!

Does the following command print the metadata?
$ /usr/sbin/crm_resource --show-metadata=ocf:heartbeat:IPaddr2

Have you got resource-agents installed?

Can you add the resource using the Pacemaker tools?  Try this:
$ sudo cibadmin --create --scope=resources --xml-text='
<primitive id="virtual-ip" class="ocf" provider="heartbeat" type="IPaddr2">
  <instance_attributes id="virtual-ip-instance_attributes">
    <nvpair id="virtual-ip-instance_attributes-ip" name="ip" value="192.98.103.40"/>
    <nvpair id="virtual-ip-instance_attributes-broadcast" name="broadcast" value="192.98.103.255"/>
    <nvpair id="virtual-ip-instance_attributes-cidr_netmask" name="cidr_netmask" value="24"/>
  </instance_attributes>
  <operations>
    <op id="virtual-ip-monitor-15" interval="15" name="monitor"/>
  </operations>
</primitive>'
-- 
Regards,
Feri.