Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ 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".
Comment 2RHEL Program Management
2023-10-09 08:56:59 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 3RHEL Program Management
2023-10-09 09:02:04 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.