I got the impression it won't be fixed. Puppet has been acquired by Perforce and will only allow registered users a maximum of 25 nodes to be managed. It's no longer fully Open Source. Time to move to Ansible, Chef, CfEngine, ...
https://www.puppet.com/blog/open-source-puppet-updates-2025 On Wednesday, April 9, 2025 at 12:35:12 AM UTC+10 rbmr...@gmail.com wrote: > Hi Team, > We are encountering a widespread issue with our Puppet client > machines, where repository updates are failing due to invalid GPG > signatures. This is preventing us from installing the Puppet agent on newly > built machines. Are there any alternative solutions or workarounds > available?" > > "W: An error occurred during the signature verification. The repository is > not updated and the previous index files will be used. GPG error: > http://apt.puppet.com jammy InRelease: The following signatures were > invalid: EXPKEYSIG 4528B6CD9E61EF26 Puppet, Inc. Release Key (Puppet, Inc. > Release Key) <rel...@puppet.com> > W: Failed to fetch http://apt.puppet.com/dists/jammy/InRelease The > following signatures were invalid: EXPKEYSIG 4528B6CD9E61EF26 Puppet, Inc. > Release Key (Puppet, Inc. Release Key) <rel...@puppet.com> > W: Some index files failed to download. They have been ignored, or old > ones used instead." > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/puppet-users/5427aae8-d488-4d45-a533-d28b7d261b19n%40googlegroups.com.
