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:	pcs	Assignee:	Tomas Jelinek <tojeline>
Status:	CLOSED MIGRATED	QA Contact:	cluster-qe <cluster-qe>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.0	CC:	cluster-maint, idevat, mlisik, mmazoure, mpospisi, omular, slevine, tojeline
Target Milestone:	rc	Keywords:	FutureFeature, MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-22 19:51:09 UTC	Type:	Story
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

Comment 7 RHEL Program Management 2023-09-22 19:49:20 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 8 RHEL Program Management 2023-09-22 19:51:09 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.