Comment 7 for bug 1749280

The root cause was the stable version of the hacluster charm not handling json serialized relation data.

James Page landed this fix.

https://review.openstack.org/#/c/545521/

My change above is still worth landing. Currently testing both.

--- Root Cause ---

root@juju-a8f1ad-mojo-26:/var/lib/juju/agents/unit-gnocchi-0/charm# relation-get -r ha:44 - gnocchi/0
corosync_bindiface: eth0
corosync_mcastport: "4440"
egress-subnets: 10.5.0.18/32
ingress-address: 10.5.0.18
json_clones: '{"cl_res_gnocchi_haproxy": "res_gnocchi_haproxy"}'
json_groups: '{"grp_gnocchi_vips": "res_gnocchi_ens3_vip"}'
json_init_services: '["haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",
  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",
  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",
  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",
  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",
  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy"]'
json_resource_params: '{"res_gnocchi_ens3_vip": " params ip=\"10.5.150.86\" nic=\"ens3\"
  cidr_netmask=\"255.255.0.0\"", "res_gnocchi_haproxy": " op monitor interval=\"5s\""}'
json_resources: '{"res_gnocchi_ens3_vip": "ocf:heartbeat:IPaddr2", "res_gnocchi_haproxy":
  "lsb:haproxy"}'
private-address: 10.5.0.18

root@juju-a8f1ad-mojo-26:/var/lib/juju/agents/unit-gnocchi-0/charm# crm status
Last updated: Sat Feb 17 00:17:12 2018 Last change: Fri Feb 16 21:45:55 2018 by root via cibadmin on juju-a8f1ad-mojo-26
Stack: corosync
Current DC: juju-a8f1ad-mojo-26 (version 1.1.14-70404b0) - partition with quorum
3 nodes and 0 resources configured

Online: [ juju-a8f1ad-mojo-26 juju-a8f1ad-mojo-27 juju-a8f1ad-mojo-28 ]

Full list of resources: