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.
DescriptionChristine Caulfield
2013-08-20 09:44:41 UTC
Clone of bug, to cover the pcs work necessary to provide this functionality.
+++ This bug was initially created as a clone of Bug #998882 +++
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.
Once corosync has support for reloading the config this should be relatively easy to add to pcs/pcsd.
Comment 3Christine Caulfield
2013-09-16 08:17:41 UTC
The code is now in corosync, once the new corosync.conf is installed on all cluster nodes the command corosync-cfgtool -R will cause it to be reloaded.
The flag config.reload_in_progress can be used by applications to detect this. See the man cmap_keys(5) for information.
A command has been added to pcs to specifically reload corosync
[cfeist@gold pcs]$ ./pcs cluster reload -h
Usage: pcs cluster reload...
reload corosync
Reload the corosync configuration on the current node
Comment 5Fabio Massimo Di Nitto
2013-10-30 03:26:33 UTC
(In reply to Christine Caulfield from comment #3)
> The code is now in corosync, once the new corosync.conf is installed on all
> cluster nodes the command corosync-cfgtool -R will cause it to be reloaded.
>
> The flag config.reload_in_progress can be used by applications to detect
> this. See the man cmap_keys(5) for information.
Chrissie, does corosync-cfgtool -R triggers a cluster wide reload or only local?
If so, then we need to change output in pcs help text.
If not, does it make sense at all to reload on one node at a time? We should probably mask the operation to be cluster wide (or at least all active cluster nodes)
Comment 7Christine Caulfield
2013-11-04 09:11:23 UTC
The text needs changing. corosync-cfgtool reloads corosync.conf on ALL nodes, so it's important to make sure that the file is up-to-date on all of them before issuing the command.
Comment 10Fabio Massimo Di Nitto
2014-01-07 12:12:12 UTC
1031832 is ON_QA now.
Chris, do you need to change your code to handle a return code or another testing round is enough?
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.