Issue #21679 has been updated by Charlie Sharpsteen. Status changed from Needs More Information to Duplicate Assignee changed from Rhys Davies to Charlie Sharpsteen
Awesome, thanks for the confirmation! I'm going to close this ticket out as a duplicate of #13568 because the only viable fix for this problem is to upgrade or rebuild Ruby. ---------------------------------------- Bug #21679: Puppet defaults to A record on an IPv6 only client in a dual stack environment. https://projects.puppetlabs.com/issues/21679#change-95271 * Author: Rhys Davies * Status: Duplicate * Priority: Normal * Assignee: Charlie Sharpsteen * 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.
