-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
FutureFeature
-
rhel-sst-high-availability
-
13
-
19
-
0
-
False
-
-
None
-
None
-
Enhancement
-
-
Proposed
-
None
This is a clone of issue RHEL-63186 to use for version rhel-9.7
–
Original description:
Goal
As a user, I want to get an explanation of why cib push failed. Currently, pcs only says cib is not valid and dumps the cib.
Acceptance criteria
When cib-push fails, pcs runs crm_verify to get a detailed information about the reason of the cib not being accepted by pacemaker. This would only apply to 'pcs cluster cib-push' and 'pcs cluster edit' commands.
Even though users can run crm_verify on their own, integrating it to pcs cib-push would improve user experience. Also various automation tools running cib-push would benefit from this.
- clones
-
RHEL-63186 Pcs should run crm_verify upon failed 'pcs cluster cib-push' to provide more details [rhel-10]
-
- In Progress
-