Description of problem: CIB may be misconfigured in such a way that it is a valid XML and confirm to the schema. In that case, it is possible to push such CIB to pacemaker with no issues. For example: not configured or misconfigured fencing; promotable clones of non-OCF resources. Consider also running crm_verify after successfully pushing CIB to pacemaker, to report possible issues early. Note that issues reported by crm_verify may depend not only on CIB but also on current cluster status. How reproducible: Always, easily Steps to Reproduce: 1. create an invalid configuration, e.g. pcs resource create test1 systemd:chronyd promotable 2. run 'pcs status' 3. Actual results: Only several cases are covered by pcs checks, non-OCF promotable clone is not. Expected results: Pcs prints all errors and warnings provided by crm_verify