This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2182383 - Both pacemaker-controld and pacemaker-schedulerd metadata contains 'no-quorum-policy' cluster property
Summary: Both pacemaker-controld and pacemaker-schedulerd metadata contains 'no-quorum...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: pacemaker
Version: 9.2
Hardware: All
OS: All
high
low
Target Milestone: rc
: 9.4
Assignee: Reid Wahl
QA Contact: cluster-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-28 13:54 UTC by Miroslav Lisik
Modified: 2023-09-22 20:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
This will primarily be for use by pcs rather than end users
Clone Of:
Environment:
Last Closed: 2023-09-22 20:07:36 UTC
Type: Story
Target Upstream Version: 2.1.7
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-7702 0 None Migrated None 2023-09-22 20:06:36 UTC
Red Hat Issue Tracker RHELPLAN-153272 0 None None None 2023-03-28 13:55:20 UTC

Internal Links: 2217850

Description Miroslav Lisik 2023-03-28 13:54:34 UTC 
Description of problem:
Both pacemaker-controld and pacemaker-schedulerd metadata contains 'no-quorum-policy' cluster property.

Version-Release number of selected component (if applicable):
pacemaker-2.1.5-7.el9

How reproducible:
always



Steps to Reproduce:
/usr/libexec/pacemaker/pacemaker-controld metadata | grep no-quorum-policy
/usr/libexec/pacemaker/pacemaker-schedulerd metadata | grep no-quorum-policy


Actual results:
Cluster property metadata for 'no-quorum-policy' is defined on both places.

Expected results:
Cluster property metadata for 'no-quorum-policy' is defined only in one deamon metadata.

Additional info:
Comment 1 Ken Gaillot 2023-03-28 14:23:30 UTC 
This is not a bug per the current Pacemaker design -- each daemon defines metadata for the cluster options that it uses, and certain options are used by both the controller and scheduler. Then "enable-acl" and "cluster-ipc-limit" are used by the CIB manager (which doesn't have a metadata option) but not the controller or scheduler, so they aren't documented in metadata anywhere.

Of course, that's not an ideal design, so we can use this bz as a feature request for a single comprehensive list of cluster option metadata, similar to Bug 2163699 for meta-attributes.
Comment 2 Tomas Jelinek 2023-03-28 14:51:49 UTC 
(In reply to Ken Gaillot from comment #1)
> Then "enable-acl" and "cluster-ipc-limit" are used by the CIB manager (which doesn't have a metadata option) but not the controller or scheduler, so they aren't documented in metadata anywhere.

They are documented in metadata in pacemaker-based. Pcs reads and processes metadata from pacemaker-based, otherwise it wouldn't consider "enable-acl" and "cluster-ipc-limit" to be allowed cluster properties and would require --force to be specified for them to be set.

> This is not a bug per the current Pacemaker design -- each daemon defines metadata for the cluster options that it uses, and certain options are used by both the controller and scheduler.

Just to put this bz into context:
The problem is that 'pcs property describe' then prints "no-quorum-policy" twice. And when validating a value of the property, pcs chooses one of the duplicate definitions. That's not a big deal now, but if the definitions ever start to differ, it will become a problem.
Comment 3 Ken Gaillot 2023-03-28 14:58:02 UTC 
(In reply to Tomas Jelinek from comment #2)
> (In reply to Ken Gaillot from comment #1)
> > Then "enable-acl" and "cluster-ipc-limit" are used by the CIB manager (which doesn't have a metadata option) but not the controller or scheduler, so they aren't documented in metadata anywhere.
> 
> They are documented in metadata in pacemaker-based. Pcs reads and processes
> metadata from pacemaker-based, otherwise it wouldn't consider "enable-acl"
> and "cluster-ipc-limit" to be allowed cluster properties and would require
> --force to be specified for them to be set.

Huh, I always thought it didn't for some reason. Well, that's good :)
 
> > This is not a bug per the current Pacemaker design -- each daemon defines metadata for the cluster options that it uses, and certain options are used by both the controller and scheduler.
> 
> Just to put this bz into context:
> The problem is that 'pcs property describe' then prints "no-quorum-policy"
> twice. And when validating a value of the property, pcs chooses one of the
> duplicate definitions. That's not a big deal now, but if the definitions
> ever start to differ, it will become a problem.

Yep, it's just a limitation of the current design. They should always be identical (it would be a bug if they weren't).
Comment 5 RHEL Program Management 2023-09-22 20:05:01 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 6 RHEL Program Management 2023-09-22 20:07:36 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.
Note You need to log in before you can comment on or make changes to this bug.