This is a clone of issue RHEL-7681 to use for version rhel-9.7
–
Original description:
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.

• This has been considered and the final decision is not to do it with the following reasoning:
  • crm_verify is already being run upon failed push of user provided CIB: RHEL-63186
  • if a pcs command is run when there is already an issue with the CIB, the resulting error messages would be confusing
  • it is responsibility of pcs to prevent creating invalid CIB and report such errors early
• pcs will, however be running crm_verify upon pushing user provided CIB even if the push succeeded

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