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.
Created attachment 1090140[details]
Proposed patch
Description of problem:
The thesis contains this paragraph:
"The Join timeout is shorter than the Consensus timeout and is used
to increase the probability that Join messages from all currently
working processors are received during a single round of
consensus."
Empirically I can confirm that making join less than consensus can
cause havoc with a cluster so I think we should enforce this.
Version-Release number of selected component (if applicable):
1.4.7
Expected results:
Set consensus timeout < join_timeout result is
"The consensus timeout parameter (X ms) may not be less than join timeout (X ms)"
Additional info:
This is change in coroparse which is not used directly when using cman, so this is SanityOnly.
Created attachment 1090141[details]
Proposed patch 2
config: Fix 'then' for 'than' typos in messages and some comments.
Also fix a 'delier' for 'deliver', which I only spotted because the line
had a (correct) 'then' on it!
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-2016-0753.html
Created attachment 1090140 [details] Proposed patch Description of problem: The thesis contains this paragraph: "The Join timeout is shorter than the Consensus timeout and is used to increase the probability that Join messages from all currently working processors are received during a single round of consensus." Empirically I can confirm that making join less than consensus can cause havoc with a cluster so I think we should enforce this. Version-Release number of selected component (if applicable): 1.4.7 Expected results: Set consensus timeout < join_timeout result is "The consensus timeout parameter (X ms) may not be less than join timeout (X ms)" Additional info: This is change in coroparse which is not used directly when using cman, so this is SanityOnly.