-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
rhel-10.0
-
None
-
No
-
Low
-
rhel-ha
-
3
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
Based on pacemaker metadata, the type of 'stonith-max-attempts' cluster property should be score, however pacemaker validator for this property is positive integer.
Please provide the package NVR for which the bug is seen:
pacemaker-3.0.0-5.el10.x86_64
How reproducible is this bug?:
always
Steps to reproduce
# /usr/sbin/crm_attribute --list-options cluster --output-as xml
{...}
<parameter name="stonith-max-attempts" advanced="0" generated="0">
<longdesc lang="en">How many times fencing can fail before it will no longer be immediately re-attempted on a target</longdesc>
<shortdesc lang="en">How many times fencing can fail before it will no longer be immediately re-attempted on a target</shortdesc>
<content type="score" default="10"/>
</parameter>
Trying to set a negative value for this property:
# pcs property set stonith-max-attempts=-10
# pcs property | grep stonith-max-attempts
stonith-max-attempts=-10
# journalctl -f -n0 -u pacemaker
{...} error: Using default value for cluster option 'stonith-max-attempts' because '-10' is invalid
Actual results
It seems like the value set for the property is -10 but actually its runtime value is 10 (default)
Expected results
Probably changing the metadata type of the property so that it reflects the validation
