Bug 742999
Summary: | [RFE] - Enhance corosync rrp | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Friesse <jfriesse> | ||||||||
Component: | corosync | Assignee: | Jan Friesse <jfriesse> | ||||||||
Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> | ||||||||
Severity: | low | Docs Contact: | Steven J. Levine <slevine> | ||||||||
Priority: | high | ||||||||||
Version: | 6.2 | CC: | cluster-maint, jkortus, jpokorny, tlavigne | ||||||||
Target Milestone: | rc | Keywords: | FutureFeature | ||||||||
Target Release: | 6.3 | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | corosync-1.4.7-2.el6 | Doc Type: | Enhancement | ||||||||
Doc Text: |
corosync now tests for correct network interface configuration in RRP mode
RRP does not work when the IP address/port number pairs are the same or the IP versions are mixed. Corosync now checks whether the network interfaces have a different IP address/port number pair and whether they use the same IP version.
|
Story Points: | --- | ||||||||
Clone Of: | |||||||||||
: | 1208151 (view as bug list) | Environment: | |||||||||
Last Closed: | 2015-07-22 07:24:47 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: | |||||||||||
Bug Blocks: | 749669, 1208151 | ||||||||||
Attachments: |
|
Description
Jan Friesse
2011-10-03 14:40:49 UTC
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. - Document (man page) that user should not use same mcast addr for rrp Created attachment 958614 [details]
config: Make sure user doesn't mix IPv6 and IPv4
config: Make sure user doesn't mix IPv6 and IPv4
Checking code was there, sadly not correct, so it was possible to enter
one bindnet addr as IPv4 and second as IPv6. Fix is trivial.
Signed-off-by: Jan Friesse <jfriesse>
Reviewed-by: Christine Caulfield <ccaulfie>
Created attachment 958615 [details]
config: Process broadcast option consistently
config: Process broadcast option consistently
Broadcast option is global but in config set in interface section. When
more interfaces are defined, only broadcast from last section was used.
Solution is to use broadcast whenever at least one interface use
broadcast.
Signed-off-by: Jan Friesse <jfriesse>
Reviewed-by: Christine Caulfield <ccaulfie>
Created attachment 958616 [details]
config: Ensure mcast address/port differs for rrp
config: Ensure mcast address/port differs for rrp
When using multiple interfaces, it's necessary to use different
multicast address/port pair for each interface to make
rrp work correctly. This is now checked in parser.
Signed-off-by: Jan Friesse <jfriesse>
Reviewed-by: Christine Caulfield <ccaulfie>
As discussed, please consider documenting, in cluster.conf(5), the restrictions and silent implications of using broadcast: - only makes sense with udp transport - if used on a ring, it will be applied to all the rings (true?) etc. These pieces of information are missing also in needle major version. 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-1389.html |