Goal

As a user, I want to get an explanation of why cib push failed. Currently, pcs only says cib is not valid and dumps the cib.

Acceptance criteria

When cib-push fails, pcs runs crm_verify to get a detailed information about the reason of the cib not being accepted by pacemaker. This would only apply to 'pcs cluster cib-push' command.

Even though users can run crm_verify on their own, integrating it to pcs cib-push would improve user experience. Also various automation tools running cib-push would benefit from this.