Bug 1774143
Summary: | [Support RFE] Make it easier to raise corosync totem token | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | John Ruemker <jruemker> |
Component: | pcs | Assignee: | Ondrej Mular <omular> |
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
Severity: | medium | Docs Contact: | Steven J. Levine <slevine> |
Priority: | high | ||
Version: | 8.3 | CC: | cfeist, cluster-maint, idevat, mlisik, mmazoure, mpospisi, nhostako, omular, sbradley, slevine, tojeline |
Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
Target Release: | 8.4 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | pcs-0.10.7-3.el8 | Doc Type: | Enhancement |
Doc Text: |
Feature: Allow to change corosync totem token.
Reason: Users need to raise corosync totem token to avoid fencing during temporary system unresponsiveness.
Result: New comand 'pcs cluster config update' was introduced to change corosync configuration which includes change of totem token value.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2021-05-18 15:12:05 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: | |||
Bug Blocks: | 1774149 |
Description
John Ruemker
2019-11-19 17:09:04 UTC
Related RFE filed in RHEL 7 and linked by many customers asking for ability to change arbitrary corosync values through pcs: https://bugzilla.redhat.com/show_bug.cgi?id=1173346 This request I've described here is more narrow, asking just for totem token. Proposed fix + tests in attachment 1739694 [details] (bz1667061 comment 12) Test: pcs cluster config update totem token=10000 Test: [root@r8-node-01 ~]# rpm -q pcs pcs-0.10.7-3.el8.x86_64 [root@r8-node-01 ~]# grep token /etc/corosync/corosync.conf [root@r8-node-01 ~]# pcs cluster config update totem token=3000 Sending updated corosync.conf to nodes... r8-node-01: Succeeded r8-node-02: Succeeded r8-node-01: Corosync configuration reloaded [root@r8-node-01 ~]# grep token /etc/corosync/corosync.conf token: 3000 [root@r8-node-01 ~]# corosync-cmapctl | grep token | head -1 runtime.config.totem.token (u32) = 3000 [root@r8-node-01 ~]# pcs cluster config update totem token=10000 Sending updated corosync.conf to nodes... r8-node-01: Succeeded r8-node-02: Succeeded r8-node-01: Corosync configuration reloaded [root@r8-node-01 ~]# grep token /etc/corosync/corosync.conf token: 10000 [root@r8-node-01 ~]# corosync-cmapctl | grep token | head -1 runtime.config.totem.token (u32) = 10000 Updating the totem token value has been tested along with other corosync configuration options within bz1667061. Marking verified based on bz1667061 comment19. 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 (pcs bug fix and enhancement update), 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://access.redhat.com/errata/RHEA-2021:1737 |