Bug 821352
Summary: | Corosync doesn't work with point-to-point connection | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Friesse <jfriesse> | ||||
Component: | corosync | Assignee: | Jan Friesse <jfriesse> | ||||
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 6.4 | CC: | jkortus, sdake | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | corosync-1.4.1-8.el6 | Doc Type: | Bug Fix | ||||
Doc Text: |
Cause
IP is configured as peer-to-peer (netmask /32). Corosync is started with bindnetaddr to configured IP address.
Consequence
Corosync is unable to create membership. Corosync sockets are bound to PEERs address instead of local one.
Fix
Use correct information about local ip.
Result
Corosync starts and run correctly.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2013-02-21 07:50:19 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Jan Friesse
2012-05-14 08:31:22 UTC
is netmask set properly? (In reply to comment #1) > is netmask set properly? Steve, problem is point-to-point and I believe you trust me that I'm able to correctly configure network ;). I've already found main problem. Created attachment 585210 [details]
Proposed patch
Patch to use IFA_LOCAL instead of IFA_ADDRESS.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause IP is configured as peer-to-peer (netmask /32). Corosync is started with bindnetaddr to configured IP address. Consequence Corosync is unable to create membership. Corosync sockets are bound to PEERs address instead of local one. Fix Use correct information about local ip. Result Corosync starts and run correctly. 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. http://rhn.redhat.com/errata/RHBA-2013-0497.html |