Bug 1333397
| Summary: | corosync does not start | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Marcel Kolaja <mkolaja> | ||||
| Component: | corosync | Assignee: | Jan Friesse <jfriesse> | ||||
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | ||||
| Severity: | urgent | Docs Contact: | Marie Hornickova <mdolezel> | ||||
| Priority: | urgent | ||||||
| Version: | 7.1 | CC: | akarlsso, ccaulfie, cfeist, cluster-maint, huy.vu, jfriesse, mailinglists, mdolezel, mjuricek, rcyriac, rsteiger, tojeline | ||||
| Target Milestone: | rc | Keywords: | ZStream | ||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| 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.
|
Story Points: | --- | ||||
| Clone Of: | 1289169 | Environment: | |||||
| Last Closed: | 2016-06-23 05:38:12 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1289169 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Marcel Kolaja
2016-05-05 12:19:39 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> 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 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.
New bug logged for this fix now causing corosync to fail on startup: https://bugzilla.redhat.com/show_bug.cgi?id=1352355 |