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 1078363 - Handle corosync initialization timeout in init script
Summary: Handle corosync initialization timeout in init script
Keywords:
Status: CLOSED ERRATA
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: Jan Friesse
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks: 1113520
TreeView+ depends on / blocked
 
Reported: 2014-03-19 16:35 UTC by Jan Friesse
Modified: 2015-03-05 08:26 UTC (History)
5 users (show)

Fixed In Version: corosync-2.3.3-3.el7
Doc Type: Bug Fix
Doc Text:
Cause: Token timeout set to large value (>= 10 sec) Consequence: Corosync may need longer time to create initial membership. Init script (unit file) waits for initial membership for maximum of 10 seconds so init script returns error. User is unable to change 10 second timeout. Fix: Make waiting for initial membership configurable and increase default value to 60 sec. Result: User can set initial membership timeout in init script and default value is larger.
Clone Of:
Environment:
Last Closed: 2015-03-05 08:26:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
init: Make init script configurable (3.68 KB, patch)
2014-06-09 13:50 UTC, Jan Friesse 		no flags Details | Diff
init: change return value when starting corosync (977 bytes, patch)
2014-06-09 13:51 UTC, Jan Friesse 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0365 0 normal SHIPPED_LIVE corosync bug fix and enhancement update 2015-03-05 12:51:37 UTC

Description Jan Friesse 2014-03-19 16:35:45 UTC 
Description of problem:
Current init script has default 10 seconds (20 * 0.5 sec) wait time until corosync is up and it's able to reply. This value may be too small for environments where token needs to be set to larger value.

Version-Release number of selected component (if applicable):
2.3.3

How reproducible:
100%

Actual results:
If corosync is unable to create membership in 10 sec, service is restarted.

Expected results:
Make init script configurable and/or come with automatic way how to set default.

Additional info:
Comment 1 Jan Friesse 2014-06-09 13:50:50 UTC 
Created attachment 904666 [details]
init: Make init script configurable

Init script loads /etc/sysconfig/corosync (or /etc/defaults/corosync) by
default, but it didn't existed by default and also no options was
defined.

Patch adds COROSYNC_INIT_TIMEOUT (how many seconds to wait for ipc
initialization) with default value 1 minute (instead of previous 10
seconds, what may be too small value for some productions) and
COROSYNC_OPTIONS (by default empty) containing options directly
passed to corosync executable.

Specfile template is also modified to install example of init file
configuration.
Comment 2 Jan Friesse 2014-06-09 13:51:29 UTC 
Created attachment 904667 [details]
init: change return value when starting corosync

When corosync is started by systemd, it would be considered
as failed because it returns a non-zero value, even though it
starts sucessfully.
Comment 3 Jan Friesse 2014-06-09 13:59:03 UTC 
Unit test:

- Package should come with /etc/sysconfig/corosync file with COROSYNC_INIT_TIMEOUT set to 60.

- Init script should wait maximum for 60 seconds to create membership (allow IPC). I was testing by removal of corosync execution line in init script.

- After changing COROSYNC_INIT_TIMEOUT, corosync should wait for maximum for configured amount of seconds (again tested by removal of corosync execution line)
Comment 7 errata-xmlrpc 2015-03-05 08:26:51 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, 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-2015-0365.html
Note You need to log in before you can comment on or make changes to this bug.