Issue #13568 has been updated by Charlie Sharpsteen.
A footnote from #21679: This issue was caused by the Debian packagers configuring the Ruby build using the `--with-lookup-order-hack=INET` flag for the Squeeze release. The only way to change this sort of compile time configuration is to re-build Ruby. The issue was fixed in the 1.8.7.334-3 Ruby build: <http://bugs.debian.org/619209> ---------------------------------------- Bug #13568: Puppet defaults to A record on an IPv6 only client in a dual stack environment. https://projects.puppetlabs.com/issues/13568#change-95273 * Author: Greg Cockburn * Status: Closed * Priority: Normal * Assignee: Patrick Carlisle * Category: agent * Target version: * Affected Puppet version: * Keywords: ipv6 * Branch: ---------------------------------------- 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. I am running puppet on Debian Squeeze. Tried: 2.7.11-1~bpo60+1 and:2.6.2-5+squeeze4 -- 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.
