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 998882 - Provide for reload of corosync.conf
Summary: Provide for reload of corosync.conf
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: corosync
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Christine Caulfield
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 998883
TreeView+ depends on / blocked
 
Reported: 2013-08-20 09:43 UTC by Christine Caulfield
Modified: 2014-06-30 13:09 UTC (History)
6 users (show)

Fixed In Version: corosync-2.3.2-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 998883 (view as bug list)
Environment:
Last Closed: 2014-06-13 11:25:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Christine Caulfield 2013-08-20 09:43:05 UTC
Corosync as it currently is cannot reload a new corosync.conf file, only individual parameters can be changed.

We need to be able to ship a new corosync.conf file round the cluster and atomically activate it on all nodes.

Comment 2 Christine Caulfield 2013-09-16 08:15:18 UTC
Code is now in git for corosync:

commit bc47c583bdd0a021ddc9efbecc8df006fef8520e
Author: Christine Caulfield <ccaulfie>
Date:   Thu Sep 12 11:03:33 2013 +0100

    Reload: Make coroparse use a designated icmap hash table

commit 82fbffc34b3803dd75d22f37d6d9cf873b5a213b
Author: Christine Caulfield <ccaulfie>
Date:   Thu Sep 12 11:04:52 2013 +0100

    Reload: Add reload code to cfg


commit c0bfd48928a7fcd93ca1683ae5ce5de63961a2e7
Author: Christine Caulfield <ccaulfie>
Date:   Thu Sep 12 11:06:13 2013 +0100

    Reload: Add atomic reload to totemconfig


commit 1a046793cb00530d8f89df235ed0cae7d8164bfe
Author: Christine Caulfield <ccaulfie>
Date:   Thu Sep 12 11:07:10 2013 +0100

    Reload: Add atomic reload to log config


commit c6688c6e11a35d13293f9b610faca5c7beb7e5cb
Author: Christine Caulfield <ccaulfie>
Date:   Thu Sep 12 16:10:35 2013 +0100

    Reload: document config.reload_in_progress in man page

Comment 9 Ludek Smid 2014-06-13 11:25:16 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


Note You need to log in before you can comment on or make changes to this bug.