Issue #21679 has been updated by Charlie Sharpsteen. Status changed from Unreviewed to Needs More Information Assignee set to Rhys Davies
As noted in #13568, it looks like the issue is down in the Ruby socket library---which really isn't something we can touch from our end. It appears for the versions of Ruby that ship with Debain Squeeze, this situation may result from misconfiguration by the upstream packagers: - <http://bugs.debian.org/619209> - <http://www.larrysalibra.com/2009/03/11/pay4bugs-finds-ubuntu-804-ruby-on-rails-ipv6-bug/> For example, using the Ruby socket library on Squeeze to do an address lookup on puppetlabs.com fails to detect any IPV6 addresses: <pre> # ruby -e "require 'socket';Socket::getaddrinfo('puppetlabs.com', 1, Socket::AF_UNSPEC).each {|r| puts r.join ' '}" AF_INET 1 web01.puppetlabs.com 96.126.112.51 2 1 6 AF_INET 1 web01.puppetlabs.com 96.126.112.51 2 2 17 AF_INET 1 web01.puppetlabs.com 96.126.112.51 2 3 0 </pre> Whereas on Wheezy, IPV6 addresses are detected: <pre> # ruby -e "require 'socket';Socket::getaddrinfo('puppetlabs.com', 1, Socket::AF_UNSPEC).each {|r| puts r.join ' '}" AF_INET 1 web01.puppetlabs.com 96.126.112.51 2 1 6 AF_INET 1 web01.puppetlabs.com 96.126.112.51 2 2 17 AF_INET 1 web01.puppetlabs.com 96.126.112.51 2 3 0 AF_INET6 1 2600:3c00::f03c:91ff:fe93:21b3 2600:3c00::f03c:91ff:fe93:21b3 10 1 6 AF_INET6 1 2600:3c00::f03c:91ff:fe93:21b3 2600:3c00::f03c:91ff:fe93:21b3 10 2 17 AF_INET6 1 2600:3c00::f03c:91ff:fe93:21b3 2600:3c00::f03c:91ff:fe93:21b3 10 3 0 </pre> The test is to pull up the list of configure flags that were passed to ruby: ruby1.8 -e 'require "rbconfig";require "shellwords";RbConfig::CONFIG["configure_args"].shellsplit.each {|a| puts "\t" + a}' If you see `--with-lookup-order-hack=INET`, then there may be a problem. Could you try rebuilding Ruby or testing the connection on another platform that isn't using the `with-lookup-order-hack` and see if dual-stack IP is functional? ---------------------------------------- Bug #21679: Puppet defaults to A record on an IPv6 only client in a dual stack environment. https://projects.puppetlabs.com/issues/21679#change-94350 * Author: Rhys Davies * Status: Needs More Information * Priority: Normal * Assignee: Rhys Davies * Category: * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- Duplicate of Bug #13568 which was closed without a fix. Ipv6 fixes should be high up the priority list for a infrastructure configuration tool. I am running a dual stack master to support my IPv4 hosts and my IPv6 hosts. My IPv6 only hosts fail to work as puppet (or ruby) does a lookup for an “A” record which of course succeeds, and so never does a look up for a “AAAA” record. Other services are coping fine with the dual stack, (figuring out they are on a IPv6 host and trying to lookup ‘AAAA’ records first.) This of course results in a ‘network unreachable’ error when trying to retrieve file metadata and catalogue. Running Debian squeeze using the latest puppet version via puppet apt repository. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
