What were you trying to do that didn't work?

Setting value of cluster properties 'stop-orphan-resources' and 'stop-orphan-actions' using pcs

What is the impact of this issue to you?

The regression breaks workflows / procedures / scripts which configure these properties.

Please provide the package NVR for which the bug is seen:

pacemaker-3.0.1-755.fabe386708.git.el10.x86_64

How reproducible is this bug?:

always, easily

Steps to reproduce

• crm_attribute --list-options cluster --output-as xml

Expected results

'crm_attribute --list-options cluster --output-as xml' lists 'stop-orphan-resources' and 'stop-orphan-actions' properties as deprecated and replaced with their new variants, so that pcs recognizes both the deprecated and new properties as valid. Deprecation is done according to OCF spec https://github.com/ClusterLabs/OCF-spec/

Actual results

Only new properties are listed in properties definition, which causes pcs to reject deprecated properties as not valid.