Hi Daniel, Yep, using the hostname works correctly - we just had quite a few failed puppet runs and the cause was unable to talk to the upstream repos.
Performing a yum clean all and letting it do its thing has things working again - appreciate the quick response. Having a bunch of IPv6 only machines has its positives.. as well as its negatives :-) Cheers David On Thursday, 7 May 2015 08:43:13 UTC+9:30, Daniel Dreier wrote: > > On Wed, May 6, 2015 at 4:06 PM, David LeVene <dle...@advisns.com.au > <javascript:>> wrote: > >> Hey All, >> >> Have quite a few machines which use IPv6 only and it looks like the >> upstream repo is possibly broken? >> >> # host yum.puppetlabs.com >> yum.puppetlabs.com is an alias for burji3.puppetlabs.com. >> burji3.puppetlabs.com has address 192.155.89.90 >> burji3.puppetlabs.com has IPv6 address 2600:3c03::f03c:91ff:fedb:6b1d >> >> http://[2600:3c03::f03c:91ff:fedb:6b1d]/el/6/dependencies/x86_64/ is >> reporting not found - No issues with IPv4. This issue started happening >> about 16 hours ago. >> >> > David - > > I just investigated that issue earlier today and thought we'd resolved it. > It was tracked in https://tickets.puppetlabs.com/browse/CPR-185, which I > believe is a public ticket. I'll investigate again and will follow up with > you out of band to figure out what's going on. > > Daniel > > -- > Daniel Dreier > Technical Operations Engineer > GPG: BA4379FD > -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/7cf5b61a-f299-4e02-850c-d428461ebff5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
