Expired GPG Key causes node installation to fail in Puppet Enterprise 2016.2 and earlier

Charlie Sharpsteen
  • Updated
Did this solve your problem?
4 out of 6 found this helpful
During installation of some older versions of Puppet Enterprise on Debian and Ubuntu nodes, a failure might occur when PE packages are being added to the system. The GPG key bundled with PE version...

Read this full article with Puppet Support

Sign in to your account Learn more about Puppet products
Can't sign in? Get help

Related articles

Comments

3 comments

Date Votes
  • Abhinav Santi

    Hello,

    The article above says only about new installations.How do I update the expired keys for existing nodes?

    Thanks in advance!

    0
  • Suzie Baunsgard
    • Edited

    Hi, it's possible that this might help you: https://support.puppet.com/hc/en-us/articles/236358027 . If it does let me know and I'll go ahead and add the link at the top to help people find it.

    I've asked the person who wrote the article to come take a look as well, so we can get you some help on this.

    0
  • Charlie Sharpsteen

    Hi Abhinav,

     

    Access to an unexpired GPG key is only required when installing or upgrading the puppet-agent package on a Debian or Ubuntu node. For the case of an upgrade, I would recommend upgrading to at least the latest LTS release (2016.4.3 as of this posting) which is unaffected by the expired GPG key.

    If the question is about an expired _agent certificate_ and not the package GPG key, then the article Suzie linked should provide a good starting point for getting a new agent certificate set up.

    Hope this helps!

    0

Please sign in to leave a comment.