Bug 2136483

Summary: [RFE] Put 'crm_verify' messages in 'pcs status' output, run 'crm_verify' when editing CIB
Product: Red Hat Enterprise Linux 9 Reporter: Tomas Jelinek <tojeline>
Component: pcsAssignee: Tomas Jelinek <tojeline>
Status: NEW --- QA Contact: cluster-qe <cluster-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0CC: cluster-maint, idevat, mlisik, mmazoure, mpospisi, omular, slevine, tojeline
Target Milestone: rcKeywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2136477    
Bug Blocks:    

Description Tomas Jelinek 2022-10-20 11:58:05 UTC 
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