Re: [Puppet Users] apt key expired

[stide...@gmail.com]

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.

https://www.puppet.com/blog/open-source-puppet-updates-2025

On Wednesday, April 9, 2025 at 12:25:40 AM UTC+10 rbmr...@gmail.com wrote:

>
> Hi Tom,
>   Encountered a GPG error while updating the Puppet repository. 
> The error message indicates an expired key 4528B6CD9E61EF26. How can I 
> resolve this issue, and is there an estimated timeframe for a fix from 
> Puppet?
> On Tuesday, April 8, 2025 at 1:53:21 AM UTC+5:30 t...@nalca.bio wrote:
>
>> On Mon, Apr 7, 2025 at 4:12 PM Dietrich, Stefan  
>> wrote:
>>
>>> Hello Tom,
>>>
>>> the future key [1] still works. It has the same ID as 
>>> DEB-GPG-KEY-puppet-20250406, but without an expiry date.
>>>
>>> Regards,
>>> Stefan
>>>
>>> [1] https://apt.puppet.com/DEB-GPG-KEY-future
>>
>>
>> Hi Stefan,
>>
>> Thanks for taking the time to respond. Sorry, I should have been more 
>> specific in my initial message. I'm trying to extend the bolt container 
>> image, like 
>> https://github.com/nalcabio/containers/blob/main/containers.d/bolt/Containerfile.
>>  
>> Do you mean I should somehow replace the offending entry under 
>> /etc/apt/sources.d with this as the signing key? Actually, now that I think 
>> I bout it, given the packages I'm trying to install, I could just delete it 
>> completely... Thanks again.
>>
>> Thanks,
>> -Tom
>>
>>  
>>
>

-- 
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/bad08216-d815-4598-987f-3f7c432004ean%40googlegroups.com.

[Puppet Users] Re: signatures were invalid: EXPKEYSIG 4528B6CD9E61EF26

[stide...@gmail.com]

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) 
> 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) 
> 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.