Hello,
thanks for confirming there's nothing wrong on the apt.puppetlabs.com side!
That leaves our testbed's networking setup as the most likely culprit then.
Either way, we'll set up a caching proxy to reduce the load we are causing
on upstream repositories now.
Cheers,
Johannes
Am Freitag,
On 2014-08-06 11:11, Johannes Grassler wrote:
> Hello,
>
> we are currently creating and tearing down lots of VMs in our lab
> environment. This includes retrieving and installing Puppet from the
> Puppetlabs repository at apt.puppetlabs.com.
Not an answer to your question directly, but for lab
Johannes,
I don't see anything on our end that would be causing the issue you're
seeing. I have enabled some additional logging on the apt repos to get
us extra information about what might be going on. I have also opened
a ticket https://tickets.puppetlabs.com/browse/CPR-60 to track this
issue. P
Hello,
we are currently creating and tearing down lots of VMs in our lab
environment. This includes retrieving and installing Puppet from the
Puppetlabs repository at apt.puppetlabs.com. Recently we found that from
some addresses in our lab's /24 access to http://apt.puppetlabs.com is
painfull
