+++ This bug was initially created as a clone of Bug #2123570 +++

Description of problem:

There are no error checks or warnings when setting invalid resource meta attributes. This can lead to unexpected behaviors for users who believed they set a valid option.

Version-Release number of selected component (if applicable):

[root@clusterb-rhel9 ~]# rpm -q pcs
pcs-0.11.1-10.el9_0.1.x86_64

How reproducible:

Set an invalid meta attribute to either a specific resource or for resource defaults:

[root@clusterb-rhel9 ~]# pcs resource defaults update resource-sti=1000
Warning: Defaults do not apply to resources which override them with their own defined values

[root@clusterb-rhel9 ~]# pcs resource update dummy1 meta resource-sti=100

Actual results:

This results in an update to the configuration, but the values won't actually do anything since the attribute are invalid:

[root@clusterb-rhel9 ~]# pcs config
------------------->8------------------
Resources:
Resource: dummy1 (class=ocf provider=heartbeat type=Dummy)
Meta Attrs: resource-sti=100
------------------->8------------------
Resources Defaults:
Meta Attrs: build-resource-defaults
resource-sti=1000
resource-stickiness=1

Expected results:

A warning or error that prevents an update to configuration, and requests additional "--force" option to set invalid values.

— Additional comment from RHEL Program Management on 2022-09-02 01:41:02 UTC —

The keyword FutureFeature has been added. If this bug is not a FutureFeature, please remove from the Summary field any strings containing "RFE, rfe, FutureFeature, FEAT, Feat, feat".