Hi Pablo (or anyone with IPv6 connectivity), can you please check if branch "fix/inventory-with-ipv6" on https://github.com/riccardomurri/elasticluster fixes the issue?
The reason why only *some* nodes were affected is likely this: once the VMs have been started, ElastiCluster probes SSH connection to the nodes, trying all the returned IP addresses in a round-robin fashion. Now, if *both* the IPv4 and the IPv6 address are responding, then which one is selected as the actual connection address is just a matter of chance. (Still, one would expect a 50/50 split, whereas your inventory shows more of a 80/20 but I do not have an explanation for that.) Ciao, R -- Riccardo Murri / Email: [email protected] / Tel.: +41 77 458 98 32 -- You received this message because you are subscribed to the Google Groups "elasticluster" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
