corosync unicast mode not selecting ipv6 addresses for nodes

Bug #1461145 reported by Edward Hope-Morley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hacluster (Juju Charms Collection)
Fix Released
High
Edward Hope-Morley

Bug Description

nodelist {

        node {
               ring0_addr: 10.5.21.23
               nodeid: 1000
        }

        node {
               ring0_addr: 10.5.21.22
               nodeid: 1001
        }

}

Related branches

Changed in hacluster (Juju Charms Collection):
milestone: none → 15.07
assignee: nobody → Edward Hope-Morley (hopem)
importance: Undecided → High
status: New → In Progress
Revision history for this message
Edward Hope-Morley (hopem) wrote :

There appears to be no check or selection happening if prefer-ipv6=True and corosync_transport=unicast when building the node list for corosync.conf. If this was running in a pure ipv6 environment (and there were no ipv4 addresses) it might not be an issue but we do support dual stack so will need to fix this.

tags: added: openstack sts
tags: added: backport-potential
Changed in hacluster (Juju Charms Collection):
status: In Progress → Fix Committed
James Page (james-page)
Changed in hacluster (Juju Charms Collection):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.