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.

It would be beneficial, at least for "static config -> pcs commands"
translation to be able to set arbitrary value in corosync.conf.

Best if implemented in a clever way that would use the knowledge
which sections/options can be sensibly repeated (like uidgid section)
and conversely, which should be treated as singleton values
(vast majority;  in reality, IIRC, when specified more than once,
the last instance wins).

Implementation-wise, this would also simplify changes like [1]
by translating, e.g.,

  --token_coefficient 5

to

  --corosync-set totem.token_coefficient=5

prior to handling.


BTW. the metadata for describing the option meaning could be extracted
from "corosync-schema" change I proposed back then:

  https://github.com/jfriesse/corosync/tree/topic-relax-conf-gen

and I even use the schema in clufter right now(!):

  https://github.com/jnpkrn/clufter/blob/v0.3.0/formats/corosync/corosync.rng



[1] https://github.com/feist/pcs/pull/44/files

Allowing something similar for CMAN-backed Pacemaker cluster is also
an option but not needed for clufter purposes.

Which settings are possible to be changed in runtime:
https://github.com/corosync/corosync/wiki/Config-file-values

Tomas,

It would be great to add nodefile.node.x.name to this list.

Note that some precautions should be taken, such as when logging to
file gets configured: [bug 1615420 comment 2].

This is on top of possible schema-based validation ([comment 0]).

Considering the current RHEL 7 life cycle stage, there will be no fix for RHEL 7.
In RHEL 8 this has been or will be fixed shortly by: bz1667061 bz1667058

*** This bug has been marked as a duplicate of bug 1667061 ***