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 1333397 - corosync does not start
Summary: corosync does not start
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: corosync
Version: 7.1
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Jan Friesse
QA Contact: cluster-qe@redhat.com
Marie Hornickova
URL:
Whiteboard:
Depends On: 1289169
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-05 12:19 UTC by Marcel Kolaja
Modified: 2016-07-12 09:42 UTC (History)
12 users (show)

Fixed In Version: corosync-2.3.4-7.el7_2.2
Doc Type: Bug Fix
Doc Text:
Previously, the corosync configuration file was generated with nodes using a hostname instead of an IP address and using the Internet Protocol version 4 (IPv4). However, the DNS server was set to return both IPv4 and IPv6 addresses. As a consequence, the corosync utility failed on start. With this update, if the corosync parser is configured to use IPv4, it uses only IPv4. As a result, corosync starts in the described circumstances as expected.
Clone Of: 1289169
Environment:
Last Closed: 2016-06-23 05:38:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
7.2.z-bz1333397-1-totemconfig-Explicitly-pass-IP-version (2.43 KB, patch)
2016-05-06 12:53 UTC, Jan Friesse 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1291 0 normal SHIPPED_LIVE corosync bug fix update 2016-06-23 09:22:05 UTC

Description Marcel Kolaja 2016-05-05 12:19:39 UTC 
This bug has been copied from bug #1289169 and has been proposed
to be backported to 7.2 z-stream (EUS).
Comment 3 Jan Friesse 2016-05-06 12:53:54 UTC 
Created attachment 1154615 [details]
7.2.z-bz1333397-1-totemconfig-Explicitly-pass-IP-version

totemconfig: Explicitly pass IP version

If resolver was set to prefer IPv6 (almost always) and interface section
was not defined (almost all config files created by pcs), IP version was
set to mcast_addr.family. Because mcast_addr.family was unset (reset to
zero), IPv6 address was returned causing failure in totemsrp.
Solution is to pass correct IP version stored in
totem_config->ip_version.

Patch also simplifies get_cluster_mcast_addr. It was using mix of
explicitly passed IP version and bindnet IP version.

Also return value of get_cluster_mcast_addr is now properly checked.

Signed-off-by: Jan Friesse <jfriesse>
Reviewed-by: Christine Caulfield <ccaulfie>
Comment 7 errata-xmlrpc 2016-06-23 05:38:12 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://access.redhat.com/errata/RHBA-2016:1291
Comment 8 Sam McLeod 2016-07-04 01:12:55 UTC 
Interestingly, after applying this updated corosync package our installations of corosync now fail to start, where they used to work as expected.

The error logged is:

Jul 04 11:09:49 s1-san8 corosync[15865]:   [MAIN  ] Corosync Cluster Engine exiting with status 8 at main.c:1250.
Jul 04 11:09:49 s1-san8 corosync[15865]:   [MAIN  ] Can't autogenerate multicast address
Jul 04 11:09:49 s1-san8 corosync[15865]:   [MAIN  ] Corosync built-in features: dbus systemd xmlconf snmp pie relro bindnow
Jul 04 11:09:49 s1-san8 corosync[15865]:   [MAIN  ] Corosync Cluster Engine ('2.3.4'): started and ready to provide service.

I will log a new bug as suggested in the final post.
Comment 9 Sam McLeod 2016-07-04 01:28:55 UTC 
New bug logged for this fix now causing corosync to fail on startup: https://bugzilla.redhat.com/show_bug.cgi?id=1352355
Note You need to log in before you can comment on or make changes to this bug.