It seems that bug related to incorrect settings for ns_IPADDR2 (/var/lib/heartbeat/trace_ra/ns_IPaddr2), that can't up vip__management.
When I've tried to restart vip__management resource I saw ERROR message in syslog
<27>Nov 18 12:39:22 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 18 12:39:22 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 18 12:39:25 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
It seems that bug related to incorrect settings for ns_IPADDR2 (/var/lib/ heartbeat/ trace_ra/ ns_IPaddr2) , that can't up vip__management.
When I've tried to restart vip__management resource I saw ERROR message in syslog
<27>Nov 18 12:39:22 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 18 12:39:22 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov 18 12:39:25 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
I've enabled trace for the resource: paste.ubuntu. com/23495234/ stop resource paste.ubuntu. com/23495235/ start resource
http://
http://
The errors is related to "undef" values from vip__* configuration those are passed to ocf script
and call ocf step with invalid values:
ocf_run ip netns exec haproxy undef
ocf_run ip netns exec haproxy ip route add undef dev b_management
It seems that puppet manifests pass through the "undef" value to resources instead of ''