corosync unicast mode not selecting ipv6 addresses for nodes
Bug #1461145 reported by
Edward Hope-Morley
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 {
}
node {
}
}
Related branches
lp:~hopem/charms/trusty/hacluster/fix-unicast-ipv6
- Liam Young (community): Approve
-
Diff: 258 lines (+143/-16)3 files modifiedhooks/hooks.py (+32/-3)
hooks/utils.py (+51/-12)
unit_tests/test_hacluster_utils.py (+60/-1)
Changed in hacluster (Juju Charms Collection): | |
milestone: | none → 15.07 |
assignee: | nobody → Edward Hope-Morley (hopem) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in hacluster (Juju Charms Collection): | |
status: | In Progress → Fix Committed |
Changed in hacluster (Juju Charms Collection): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.