Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionChristine Caulfield
2015-11-16 09:04:10 UTC
Description of problem:
Multicast does not work over IPv6
corosync 2.3.5 but I suspect this goes back some way
How reproducible:
Every time
Steps to Reproduce:
1. Set up a cluster to use IPv6 multicast
2. Start nodes
Actual results:
The nodes do not see each other. corosync-quorumtool shows that all the
nodes are isolated
Expected results:
Cluster should form correctly.
Additional info:
This is specific to IPv6, IPv4 clusters are not affected. Also IPv6 clusters using updu are also fine.
Here is my corosync.conf for testing. The other node has IP address
ending in :2 of course.
totem {
version: 2
secauth: off
cluster_name: small
transport: udp
interface {
ringnumber: 0
mcastaddr: ff08::2
bindnetaddr: 2001:db8:1:0:200:11ff:fecc:1
ttl: 8
}
ip_version: ipv6
nodeid: 1
}
quorum {
provider: corosync_votequorum
expected_votes: 2
}
Comment 2Christine Caulfield
2015-11-16 09:05:54 UTC
Created attachment 1094783[details]
Patch to move the bind() so that ipV6 works
I've also tested that this patch does not break IPv4.
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-2016-2463.html
Description of problem: Multicast does not work over IPv6 corosync 2.3.5 but I suspect this goes back some way How reproducible: Every time Steps to Reproduce: 1. Set up a cluster to use IPv6 multicast 2. Start nodes Actual results: The nodes do not see each other. corosync-quorumtool shows that all the nodes are isolated Expected results: Cluster should form correctly. Additional info: This is specific to IPv6, IPv4 clusters are not affected. Also IPv6 clusters using updu are also fine. Here is my corosync.conf for testing. The other node has IP address ending in :2 of course. totem { version: 2 secauth: off cluster_name: small transport: udp interface { ringnumber: 0 mcastaddr: ff08::2 bindnetaddr: 2001:db8:1:0:200:11ff:fecc:1 ttl: 8 } ip_version: ipv6 nodeid: 1 } quorum { provider: corosync_votequorum expected_votes: 2 }