This message was deleted.

This message was deleted.

I know there is a puppet task that can be run to cleanup a node once its been removed. Maybe something in cloud_init that could trigger running that task, since I believe it has to be run on an authorized node, and you probably wouldn't want to authorize all nodes to run that command. https://support.puppet.com/hc/en-us/articles/360012551294-Clean-or-purge-nodes-using-a-task-in-Puppet-Enterprise

I did a thing a while back with Terraform for the node to log into the Server and purge itself on destroy: https://github.com/WhatsARanjit/puppetize2019/blob/master/agent/main.tf#L60-L72 Probably a terrible way to do it though. 🙂

Has anyone downloaded and installed the new tar ball for PE ? If so, how do you verify the binary ? I can't find the required asc file. gpg --verify puppet-<VERSION>.<FILE TYPE>.asc puppet-<VERSION>.<FILE TYPE> source: https://puppet.com/docs/puppet/7/verify_packages.html

i got this file: puppet-enterprise-2021.5.0-el-7-x86_64.tar.gz

i think i need this file too: puppet-enterprise-2021.5.0-el-7-x86_64.tar.gz.asc

PE wouldn't be a source tar ball. You have the installer image for PE. You want to follow the steps on this page instead: https://puppet.com/docs/pe/2021.5/installing_pe.html

It fails at step #3 if you follow the directions there. There doesn't appear to be an asc file.

This message was deleted.

You can do a verify on the opensource versions. I don't see a place to download the ASC files for PE.

[root@lpe0p tmp]# gpg --verify puppetserver-6.19.0.tar.gz.asc gpg: Signature made Fri 01 Apr 2022 041255 PM EDT using RSA key ID 9E61EF26 gpg: Good signature from "Puppet, Inc. Release Key (Puppet, Inc. Release Key) <release@puppet.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: D681 1ED3 ADEE B844 1AF5 AA8F 4528 B6CD 9E61 EF26

The opensource stuff has the asc files with the download. https://downloads.puppetlabs.com/puppet/index_by_lastModified_reverse.html

Yep, it looks like there might be a missing step in there. You can download the signature from https://pm.puppet.com/cgi-bin/download.cgi?dist=el&amp;rel=7&amp;arch=x86_64&amp;ver=latest&amp;type=sig

If you follow the "Download" link in the "Install PE" section of that page, you'll see the PGP keys listed underneath the link for the actual install bundle.

When is the next PE LTS expected to drop? Sept?

hey people. versioned deploys: If I set

puppet_enterprise::profile::master::versioned_deploys: true

on my 2021.5 primary,

/etc/puppetlabs/puppetserver/code

is a symlink to

/etc/puppetlabs/code

? Isn't that wrong? Shouldn't it point to somewhere in /opt?

Seems the problem with puppet agent not matching puppet version breaks puppet_agent module. Just updated my sandbox infra to PE2019.8.11 and module fails to update agents

Error: /Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure: change from '6.26.0-1.el7' to '6.27.0' failed: Could not update: Failed to update to version 6.27.0, got version 6.26.0-1.el7 instead

Seems the problem with puppet agent not matching puppet version breaks puppet_agent module. Just updated my sandbox infra to PE2019.8.11 and module fails to update agents

Error: /Stage[main]/Puppet_agent::Install/Package[puppet-agent]/ensure: change from '6.26.0-1.el7' to '6.27.0' failed: Could not update: Failed to update to version 6.27.0, got version 6.26.0-1.el7 instead

Found existing ticket https://tickets.puppetlabs.com/browse/MODULES-11315

We’re looking into the best fix for MODULES-11315 at the moment.

I suggest: release 6.27.1

6.27.1 would take the longest to pull together of the available options and would also involve building a PE 2019.8.12.

yes, but I think a) that's the cleanest way and ) that just points out that the release process has some options for improvements (yes I know how tricky that is)

I still say function returning server's fact is the easiest solution, no need for spawning

generate

or deal with Windows

I still say function returning server's fact is the easiest solution, no need for spawning

generate

or deal with Windows

Does

$serverversion

not work? That might be the Puppet Server itself, not the

puppet

binary: https://puppet.com/docs/puppet/7/lang_facts_builtin_variables.html#lang_facts_builtin_variables-server-variables

serverversion returns puppet version not the server's puppet agent version

it's wrong assumption as @josh said in the ticket

Hi, On one of my node Puppet is running fine in cache/non-cache mode. However, on console, I don’t see the latest reports since last few days. What should I check ? For other nodes, reporting is being done fine.