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 1856397 - [RFE] Support for reload of corosync crypto configuration
Summary: [RFE] Support for reload of corosync crypto configuration
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: pcs
Version: 8.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 8.4
Assignee: Miroslav Lisik
QA Contact: cluster-qe@redhat.com
Steven J. Levine
URL:
Whiteboard:
Depends On: 1667061 1855293 1855301 1855303
Blocks: 1457314
TreeView+ depends on / blocked
 
Reported: 2020-07-13 14:16 UTC by Jan Friesse
Modified: 2021-05-18 15:12 UTC (History)
12 users (show)

Fixed In Version: pcs-0.10.8-1.el8
Doc Type: Enhancement
Doc Text:
Feature: Provide support for reload of corosync crypto configuration. Reason: Users want to change corosync crypto configuration of an existing cluster. Result: Configuration of corosync crypto cipher and hash can be changed by using command 'pcs cluster config update' and corosync authkey can be changed by using command 'pcs cluster authkey corosync'.
Clone Of: 1855303
Environment:
Last Closed: 2021-05-18 15:12:08 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed fix + tests (50.88 KB, patch)
2021-01-28 14:47 UTC, Miroslav Lisik 		no flags Details | Diff
View All

Comment 10 Miroslav Lisik 2021-01-28 14:47:41 UTC 
Created attachment 1751730 [details]
proposed fix + tests

add new command for update corosync authkey:
* pcs cluster authkey corosync

Test:
[root@r8-node-01 pcs]# pcs cluster authkey corosync
Sending 'corosync authkey' to 'r8-node-01', 'r8-node-02'
r8-node-02: successful distribution of the file 'corosync authkey'
r8-node-01: successful distribution of the file 'corosync authkey'
r8-node-01: Corosync configuration reloaded
Comment 11 Miroslav Lisik 2021-02-01 16:43:11 UTC 
Changing crypto parameters is already covered in bz1667061.

Test:

[root@r8-node-01 ~]# rpm -q pcs
pcs-0.10.8-1.el8.x86_64

[root@r8-node-01 ~]# for node in r8-node-0{1,2}; do ssh root@r8-node-01 "md5sum /etc/corosync/authkey"; done
c66ff61b202e1b0aba39153d7fa19728  /etc/corosync/authkey
c66ff61b202e1b0aba39153d7fa19728  /etc/corosync/authkey

[root@r8-node-01 ~]# pcs cluster authkey corosync 
Sending 'corosync authkey' to 'r8-node-01', 'r8-node-02'
r8-node-01: successful distribution of the file 'corosync authkey'
r8-node-02: successful distribution of the file 'corosync authkey'
r8-node-01: Corosync configuration reloaded

[root@r8-node-01 ~]# journalctl -f -n 0 -u corosync.service
-- Logs begin at Mon 2021-02-01 11:31:16 CET. --
Feb 01 12:00:51 r8-node-01 corosync[6153]:   [CFG   ] Config reload requested by node 1
Feb 01 12:00:51 r8-node-01 corosync[6153]:   [TOTEM ] Configuring link 0
Feb 01 12:00:51 r8-node-01 corosync[6153]:   [TOTEM ] Configured link number 0: local addr: 192.168.122.81, port=5405

[root@r8-node-01 ~]# for node in r8-node-0{1,2}; do ssh root@r8-node-01 "md5sum /etc/corosync/authkey"; done
6ab9cd2114a061ee03fc396049bf448f  /etc/corosync/authkey
6ab9cd2114a061ee03fc396049bf448f  /etc/corosync/authkey
Comment 18 errata-xmlrpc 2021-05-18 15:12:08 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 (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
Note You need to log in before you can comment on or make changes to this bug.