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.

Bug 1108538

Summary: [RFE] Add support for corosync totem.token_coefficient setting
Product: Red Hat Enterprise Linux 7 Reporter: Jan Friesse <jfriesse>
Component: pcsAssignee: Chris Feist <cfeist>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: high    
Version: 7.1CC: cluster-maint, jpokorny, rsteiger, tojeline
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcs-0.9.127-1.el7 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 09:19:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1078361    
Bug Blocks:    
Attachments:
Description Flags
Proposed patch
none
proposed patch for gui none

Description Jan Friesse 2014-06-12 08:17:36 UTC 
Description of problem:
Dynamic token timeout feature of corosync (7557fdec487cb5fad7c449949ba58496bd396458 or bug 1078361) is not yet supported in current (d58336f5af61b8056456a538b7b508d2ebae9715) pcs. RFE is about adding support for change token_coefficient via pcs.

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

How reproducible:
100%

Steps to Reproduce:
1. Try to change corosync token_coefficient via pcs

Actual results:
Impossible to change token_coefficient

Expected results:
It's possible to change token_coefficient

Additional info:
Comment 1 Jan Friesse 2014-06-16 14:36:27 UTC 
Created attachment 909155 [details]
Proposed patch

Proposed patch with unit test included.

pull-request can be found at github https://github.com/feist/pcs/pull/44
Comment 2 Chris Feist 2014-09-09 20:38:46 UTC 
Fixes posted upstream here:

https://github.com/feist/pcs/commit/68ba0648fbb77863159447e9dcfa3f338c65e04e
Comment 3 Tomas Jelinek 2014-09-11 15:15:16 UTC 
Created attachment 936590 [details]
proposed patch for gui
Comment 4 Tomas Jelinek 2014-09-15 08:29:01 UTC 
Before Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.115-32.el7.x86_64
[root@rh70-node1 ~]# pcs cluster help | grep token_coefficient
[root@rh70-node1 ~]# pcs cluster setup --name cluster70 rh70-node1 rh70-node2 --token_coefficient=500
option --token_coefficient not recognized
{output trimmed}

Open 'Create Cluster' dialog in pcsd GUI. 'Token Timeout Coefficient' option is not available.


After Fix:
[root@rh70-node1 ~]# rpm -q pcs
pcs-0.9.127-1.el7.x86_64
[root@rh70-node1 ~]# pcs cluster help | grep token_coefficient
            [--ipv6] [--token <timeout>] [--token_coefficient <timeout>]
        --token_coefficient <timeout> sets time in milliseconds used for clusters
            (token + (number_of_nodes - 2) * token_coefficient) (default 650 ms)
[root@rh70-node1 ~]# pcs cluster setup --name cluster70 rh70-node1 rh70-node2 --token_coefficient=500
Shutting down pacemaker/corosync services...
Redirecting to /bin/systemctl stop  pacemaker.service
Redirecting to /bin/systemctl stop  corosync.service
Killing any remaining services...
Removing all cluster configuration files...
rh70-node1: Succeeded
rh70-node2: Succeeded
[root@rh70-node1 ~]# grep coefficient /etc/corosync/corosync.conf
token_coefficient: 500

Open 'Create Cluster' dialog in pcsd GUI. 'Token Timeout Coefficient' option is available.
Comment 7 Jan Pokorný [poki] 2014-12-11 22:12:11 UTC 
See also [bug 1173346] for a more generic approach request.
Comment 9 errata-xmlrpc 2015-03-05 09:19:55 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0415.html