-
Bug
-
Resolution: Done-Errata
-
Blocker
-
rhel-9.5
-
pcs-0.11.7-3.el9
-
None
-
Critical
-
rhel-sst-high-availability
-
ssg_filesystems_storage_and_HA
-
13
-
23
-
3
-
False
-
-
No
-
None
-
Pass
-
None
-
Release Note Not Required
-
The purpose of this ticket is to restore previous behavior after the changes done in pacemaker. There should be no visible impact on pcs once that's done.
-
None
What were you trying to do that didn't work?
Reading cluster properties definition from pacemaker doesn't work. The definition format was changes recently and it doesn't fit constraints pcs puts on it. Parsing the properties metadata needs to be updated to be able to process the new metadata format.
This affects not only working with cluster properties, but also working with stonith resources. When working with stonith resources, pacemaker-fenced metadata is being processed. Configuring utilization and acls is also affected, as pcs is trying to check whether utilization and acls is enabled, respectively.
Please provide the package NVR for which bug is seen:
pcs-0.11.7-1.el9
How reproducible:
always, easily
Steps to reproduce
- Configure or list cluster properties, create or update stonith resources, configure resource utilization or ACLs.
Expected results
It works. Cluster properties are listed with correct 'advanced' flag and list of allowed values.
Actual results
Error: Agent 'pacemaker-{name}' is not installed or does not provide valid metadata: Invalid attribute advanced for element parameter, line 12
Additional info
- Pacemaker changes: https://github.com/ClusterLabs/pacemaker/pull/3338
- Pacemaker Jira:
RHEL-23401 - Pacemaker upstream ticket: https://projects.clusterlabs.org/T620
- is related to
-
RHEL-23401 Create command-line method of listing all possible cluster options, primitive meta-attributes, and special fencing resource parameters
- Closed
- links to
-
RHBA-2024:133004 pcs bug fix and enhancement update
- mentioned on