-
Bug
-
Resolution: Done-Errata
-
Major
-
rhel-9.0.0
-
pacemaker-2.1.8-2.el9
-
None
-
Moderate
-
rhel-sst-high-availability
-
ssg_filesystems_storage_and_HA
-
21
-
26
-
2
-
QE ack, Dev ack
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
Pass
-
None
-
This is not highly visible to end users and is intended primarily for use by pcs
-
None
What were you trying to do that didn't work?
crm_verify doesn't report invalid indexes in fencing levels. According to pacemaker explained, valid values of the index are 1 through 9.
https://clusterlabs.org/pacemaker/doc/2.1/Pacemaker_Explained/singlehtml/#fencing-topologies
Please provide the package NVR for which bug is seen:
pacemaker-2.1.6-9
How reproducible:
always, easily
Steps to reproduce
- create a fencing-level with index > 9, e.g.
<fencing-level index="20" devices="xvm" target="rh92-node1" id="fl-rh92-node1-20"/>
- run crm_verify -VVVV --live-check
Expected results
crm_verify reports invalid fencing-level index
Actual results
# crm_verify -VVVV --live-check (main) info: =#=#=#=#= Getting XML =#=#=#=#= (main) info: Reading XML from: live cluster (cib_native_signon_raw) info: Successfully connected to CIB manager for crm_verify (determine_online_status_fencing) info: rh92-node1 is active (determine_online_status) info: rh92-node1 is online (pcmk__unassign_resource) info: Unassigning xvm (pcmk__unassign_resource) info: Unassigning d1 (pcmk__unassign_resource) info: Unassigning d2 (pcmk__unassign_resource) info: Unassigning d3 (rsc_action_default) info: Leave xvm (Started rh92-node1) (rsc_action_default) info: Leave d1 (Started rh92-node1) (rsc_action_default) info: Leave d2 (Started rh92-node1) (rsc_action_default) info: Leave d3 (Started rh92-node1) (crm_exit) info: Exiting crm_verify | with status 0
no mention about not valid / ignored fencing-level
- links to
-
RHBA-2024:135589
pacemaker bug fix and enhancement update
