Hi, With a bit of help from Haus we figured it out.
The last time our apt-cacher-ng pulled in the apt.puppetabs.com repo something went wrong causing a few of the files to go corrupt, triggering the validation errors. This then trickled down to all the machines when apticron ran an apt-get update. The solution was to get rid of /var/cache/apt-cacher-ng/apt.puppetlabs.com and /var/lib/apt/lists/* (and then recreating /var/lib/apt/lists/partial) on the apt-cacher-ng machine. After that, apt-get clean and apt-get update were run on the apt-cacher-ng machine. it now pulled in everything correctly and everything started working again. How the issue occurred in the first place still remains a bit of a mystery. -- Daniele Sluijters On Thursday, 10 January 2013 09:02:14 UTC+1, Daniele Sluijters wrote: > > Hi, > > I just started getting errors from APT: W: GPG error: > http://apt.puppetlabs.com squeeze Release: The following signatures were > invalid: BADSIG 1054B7A24BD6EC30 Puppet Labs Release Key (Puppet Labs > Release Key) <i...@puppetlabs.com> > > It looks like they keyring was changed yesterday on the APT repository: > keyring.gpg 09-Jan-2013 14:51 2.5K > > However, I've yet to see an announcement about this. So, was this actually > done by Puppet Labs or is something else going on? > > Kind regards, > > -- > Daniele Sluijters > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/wedxctcj09YJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
