-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-9.6, rhel-10.0
-
None
-
No
-
None
-
rhel-ha
-
3
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
Pacemker is able to detect invalid values of target-role meta attribute. Despite that, it copies the invalid values in xml status. This is wrong because a) it doesn't match the actual target role considered by pacemaker b) it makes the status xml invalid.
Reproducer:
pcs resource meta d3 target-role=invalid crm_verify -V -V --live-check error: Ignoring 'target-role' for d3 because 'invalid' is not valid (unpack_rsc_op_failure) warning: Unexpected result (Error occurred: Fence agent did not complete within 20s) was recorded for start of xvm on rh101-node1 at Jul 9 08:53:41 2025 | exit-status=1 id=xvm_last_failure_0 error: Ignoring 'target-role' for d3 because 'invalid' is not valid (pcmk__threshold_reached) warning: xvm cannot run on rh101-node1 due to reaching migration threshold (clean up resource to allow again) | failures=1000000 migration-threshold=1000000 error: CIB did not pass schema validation Configuration invalid (with errors) crm_mon --one-shot --inactive --output-as xml | grep 'resource id="d3"' <resource id="d3" resource_agent="ocf:pacemaker:Dummy" role="Started" target_role="invalid" active="true" orphaned="false" blocked="false" maintenance="false" managed="true" failed="false" failure_ignored="false" nodes_running_on="1">
Expected results:
As you can see in the crm_verify output, pacemaker detects and ignores invalid target-role. Therefore, it should put the actual target-role value (presumably the default?) it is working with into the status xml.
