cat /opt/puppetlabs/puppet/cache/state/classes.txt

This message was deleted.

the more you know Content and Tooling is about to start up in #CFD8Z9A4T

so usually each node has few roles, but they may include a lot of modules.

of coz they give us time to upgrade and test. :)

what do you mean all modules?

This message was deleted.

Hello, everyone. I’m getting the following error message:

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, 'versioncmp' parameter 'a' expects a String value, got Undef

The line:

$old_openssl = versioncmp($facts['openssl_version'], '1.1.0') < 0

I noticed the following in debug mode:

Debug: Facter: Executing command: /usr/bin/openssl version 2>&1

Debug: Facter: value for openssl_version is still nil

# /usr/bin/openssl version 2>&1

OpenSSL 1.1.1k FIPS 25 Mar 2021 I am using the latest puppet-openssl module. Any advice? Thank you!

Hello, everyone. I’m getting the following error message:

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, 'versioncmp' parameter 'a' expects a String value, got Undef

The line:

$old_openssl = versioncmp($facts['openssl_version'], '1.1.0') < 0

I noticed the following in debug mode:

Debug: Facter: Executing command: /usr/bin/openssl version 2>&1

Debug: Facter: value for openssl_version is still nil

# /usr/bin/openssl version 2>&1

OpenSSL 1.1.1k FIPS 25 Mar 2021 From `openssl_version.rb`:

matches = %r{^OpenSSL ([\w.\-]+)( FIPS)?( +)([\d.]+)( +)([\w.]+)( +)([\d.]+)}.match(openssl_version)

I am using the latest puppet-openssl module. Any advice? Thank you!

This message was deleted.

This message was deleted.

you probably have to run

puppet cert sign --lifetime 5y <certname>

but not sure.

I think. It is not possible to generate a new SSL certificate with the same key as the Puppet 6 certificate on the Puppet 7 server.

I think there was a Puppet module that had a Bolt task for modifying Puppet certs to allow for mutual trust between two distinct CA's. The use case was eaxctly this, where you're migrating agents to a new Puppet infrastructure and the agents need to trust the existing CA and the new CA. ...but I can't remember the name of the module.

message has been deleted

message has been deleted

I’d at least use dedicated set of masters & puppetdb to deal with laptops.. maybe with separate dashboards/etc

@rnelson0 you were right on point. https://github.com/voxpupuli/puppet-openssl/pull/135

Puppet Integration Releases Splunk Splunk_hec 1.4.0 This module provides three services to Puppet and Splunk users. • A report processor to allow sending Puppet Agent run reports to Splunk • A fact terminus to submit node facts to Splunk • A PE Event Forwarding processor Key features/changes: Fixed • Event filtering for

pe-console

and

code-manager

events are no longer ignored Full changelog v1.3.0 to v1.4.0 Feedback https://github.com/puppetlabs/puppetlabs-splunk_hec/issues

these are macOS and Windows devices so cron is not a direct path forward 😕

these are macOS and Windows devices so cron is not a direct path forward 😕. Also these connections generally drop during a puppet run, which on average is about 40 seconds.

Since a few days we are experiencing 'execution expired' issues with our rspec checks, which downloads modules from the forge: ERROR -> Error during concurrent deploy of a module: Unable to connect to https://forgeapi.puppet.com (for request /v3/files/puppetlabs-bolt_shim-0.4.0.tar.gz): execution expired 298ERROR -> Unable to connect to https://forgeapi.puppet.com (for request /v3/releases/puppetlabs-stdlib-8.5.0): execution expired 299Error while running: #<RuntimeError: r10k could not install all required modules> It's pretty consistent 3-5 modules that can't be downloaded. Anyone having similar issues?

do you proxy forge requests through an internal mirror? can you run r10k with debug output?

Its a gitlab runner, The runner is hosted locally in a docker container, so I guess there is some kind of proxying going on

This message was deleted.

This message was deleted.

Info: Loading facts
Warning: The `source_permissions` parameter is deprecated. Explicitly set `owner`, `group`, and `mode`.
   (file: /etc/puppetlabs/code/nodes/production/***.pp, line: 142)

And the documentation says nothing like that: https://www.puppet.com/docs/puppet/7/types/file.html#file-attribute-source_permissions I fount nothing were I can submit a PR to get the documentation changed?

This message was deleted.

This message was deleted.

This message was deleted.