-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
FutureFeature
-
rhel-sst-high-availability
-
13
-
19
-
3
-
False
-
-
None
-
None
-
None
-
None
-
Enhancement
-
-
Proposed
-
None
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.
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
- clones
-
RHEL-7681 [RFE] Put 'crm_verify' messages in 'pcs status' output, run 'crm_verify' when editing CIB [rhel-10]
-
- Planning
-