config: Look up hostnames in a defined order

Current practice is to let getaddrinfo() decide which address we get
but this is not necessarily deterministic as DNS servers won't
always return addresses in the same order if a node has
several. While this doesn't deal with node names that have
multiple IP addresses of the same family (that's an installation issue
IMHO) we can, at least, force a definite order for IPv6/IPv4 name
resolution.

I've chosen IPv6 then IPv4 as that's what happens on my test system (
using /etc/hosts) and it also seems more 'future proof'.

Signed-off-by: Christine Caulfield <ccaulfie@redhat.com>
Reviewed-by: Jan Friesse <jfriesse@redhat.com>

diff --git a/exec/totemip.c b/exec/totemip.c
index c0f753d1a1b98f65f3a8225ca03e1fbbec52664e..cb676e40e987fccfa7fb32f93aea27faf372c5d1 100644 (file)
--- a/exec/totemip.c
+++ b/exec/totemip.c
@@ -295,8 +295,17 @@ int totemip_parse(struct totem_ip_address *totemip, const char *addr, int family
        ahints.ai_protocol = IPPROTO_UDP;
        ahints.ai_family   = family;
 
-       /* Lookup the nodename address */
-       ret = getaddrinfo(addr, NULL, &ahints, &ainfo);
+       /* If no address family specified then try IPv6 first then IPv4 */
+       if (family == AF_UNSPEC) {
+               ahints.ai_family = AF_INET6;
+               ret = getaddrinfo(addr, NULL, &ahints, &ainfo);
+               if (ret) {
+                       ahints.ai_family = AF_INET;
+                       ret = getaddrinfo(addr, NULL, &ahints, &ainfo);
+               }
+       } else {
+               ret = getaddrinfo(addr, NULL, &ahints, &ainfo);
+       }
        if (ret)
                return -1;
 

diff --git a/man/corosync.conf.5 b/man/corosync.conf.5
index c33051690933f432e06f78fe92c6a7b626b8925e..2b5f743e4ada4613de9d2bfa06795b4609ae4c31 100644 (file)
--- a/man/corosync.conf.5
+++ b/man/corosync.conf.5
@@ -865,15 +865,17 @@ corosync-cfgtool -R
 on one of them.
 
 .SH "ADDRESS RESOLUTION"
-corosync resolves ringX_addr names/IP addresses using the getaddrinfo(3) call. This function uses a sophisticated
-algorithm to sort node addresses into a preferred order and corosync always chooses the first address in that list.
-If the node has both IPv4 and IPv6 addresses it is likely that the IPv6 one will be chosen but this is not guaranteed
-(see RFC3484 for more information) as the algorthm matches on prefix length and other criteria.
-
-As such it is essential that your DNS or /etc/hosts files are correctly configured so that all addresses for ringX
-appear on the same network (or are reachable with minimal hops) and over the same IP protocol. If this is not
-the case then some nodes might not be able to join the cluster. It is possible to override the search order used
-by getaddrinfo() using the configuration file /etc/gai.conf(5) if necessary, but this is not recommended.
+corosync resolves ringX_addr names/IP addresses using the getaddrinfo(3) call in two passes.
+First it will check for an IPv6 address, if that fails then it will look for an IPv4 address.
+
+getaddrinfo() function uses a sophisticated algorithm to sort node addresses into a preferred
+order and corosync always chooses the first address in that list of the required family.
+As such it is essential that your DNS or /etc/hosts files are correctly configured so that
+all addresses for ringX appear on the same network (or are reachable with minimal hops)
+and over the same IP protocol. If this is not the case then some nodes might not be able
+to join the cluster. It is possible to override the search order used
+by getaddrinfo() using the configuration file /etc/gai.conf(5) if necessary,
+but this is not recommended.
 
 If there is any doubt about the order of addresses returned from getaddrinfo() then it might be simpler to use
 IP addresses (v4 or v6) in the ringX_addr field.