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

[Juha Heinanen]

I built pacemaker 1.1.14 on Debian Jessie from Stretch source.  Built
succeeded after some changes in debian/rules and control:

In rules:

override_dh_strip:
#	dh_strip --ddeb-migration='pacemaker-dbg (<< 1.1.14~rc4-1~)'
	dh_strip --dbg-package=pacemaker-dbg

This is because --ddeb-migration option does not exist in Jessie
dh_strip.

In control:

Added entry

Package: pacemaker-dbg
Architecture: any
Section: debug
Priority: extra
Depends: pacemaker (= ${binary:Version}),
 ${misc:Depends}
Description: Debugging symbols for Pacemaker
 High-Availability cluster resource manager for Corosync.
 .
 Pacemaker supports a very sophisticated dependency model for
 n-node clusters and can respond to node and resource-level
 failures.
 .
 Since Corosync handles quorum all on its own, and is RHEL's
 recommended stack, pacemaker supports the Corosync cluster
 stack.
 .
 This package contains the debugging symbols for Pacemaker.

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

Package: pacemaker-cli-utils
Architecture: any
Depends: ${shlibs:Depends},
 ${misc:Depends},
 init-system-helpers  (>= 1.22)
 # ... because << 1.23 starts our disabled crm_mon service on install and
# upgrade, see #768456.

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

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.

-- Juha