Hi everyone ! Since doing the following :

if defined(Class['my_super_class']) {
     class { 'my_other_super_class': }
  }

Might result in an issue if the ordering in Puppet is not at our advantage, how would do the same thing ? I want to include a class, only if another class is already present.

Why?

That looks like an anti pattern

I have a main class that defines an application, and I want to make sure that if the node we apply on, has the log retrieval mechanism that we use, then we should add the small snippet of configuration for this application logs to be retrieved.

It might be an anti-pattern, but I don't really see a way to do that properly

The resource that adds the small snippet should fail with an informative error (and no change) if the overall mechanism is not present.

But I don't want the small snippet to be required for the application.. It's like that

[my_application_class]              [my_global_logs_conf_class]
   if my_global_logs_conf_class
     [my_small_logs_class]

But

my_application_class

should not fail because the

my_global_logs_conf_class

is not declared.. Maybe on this node we don't want to have the log mechanism that we have on other nodes

is this an application config settings ng? make a template.

vscode extension says that it uses puppet-lint and yet the editor is unhappy with idents and latest puppet-lint is fine. Some setting is missing?

Different linter versions?

It seems extension bundles it. I don't see a way to tell it to use a new one

Hello, everyone. What is a recommended approach to cleaning up puppet code? I have tried puppet-lint with

--only-checks ghostbuster_classes,ghostbuster_files,ghostbuster_templates

, but, for some reason, not getting any results. I’m sure i have some unused templates, manifests, etc… My google search is not pointing to any else useful. Any suggestions? Thank you!

VoxBox is probably your best bet long term https://github.com/voxpupuli/container-voxbox. But I and many others are still using the latest public release of the PDK.

pdk validate

will run the linters, and adding

-a

will do autocorrect

Also the community Slack is more active and a better place to get feedback these days https://voxpupuli.org/connect/

Hey there... THis page: https://github.com/puppetlabs/puppetserver/tree/main/documentation says the osp docs have moved and links to a nonexistent location. Can we get a fix on that? I'm trying to retrieve super-old docs. Doing some research on balancing the front end, and recalled some 2-3.x days methods I wanted to look over.

Puppet Server, the Java Service, was like laaaate 3.x. So, might not be what you're looking for if 2.x is in the time frame.

2.x, and other early docs are here: https://github.com/puppetlabs/docs-archive/tree/main/puppet

I know I was using Apache + Passenger in 2.7. I still have the configs for it on disk.

Earliest I find here is 3.8, though…. that’s after the DB change.

HAHAHA! I’m a digital pack rat:

LoadModule passenger_module /usr/lib/ruby/gems/1.8/gems/passenger-4.0.26/build  out/apache2/mod_passenger.so
     PassengerRoot /usr/lib/ruby/gems/1.8/gems/passenger-4.0.26
     PassengerDefaultRuby /usr/bin/ruby

  PassengerHighPerformance On
  PassengerMaxPoolSize 12
  PassengerPoolIdleTime 1500
  PassengerMaxRequests 1000
  PassengerStatThrottleRate 120

  Listen 8140

wow… this external drive has backups of old consulting machines long since gone. It’s a veritable archaeological dig

It's a lot easier to just huck it over to a subdirectory on long-term storage than to just delete it outright. What's fun, though? Pull in code from 2011 and run puppet-lint against it. 😄

evilest

Howdy all... I'm stumped and interested in some tips to track down how this is working. Environment: Puppetserver 7.17 and foreman 3.14. This year we've updated from old versions of Puppet... I think it was 2.7 (that was fun!) I have two hosts using a locally built proftpd module ages ago. The structure looks like it was developed with the PDK. (init and params manifests). There is a variable called $service_manage that controls if the proftpd service is managed (duh). These hosts are set up in different clusters and should have $proftpd::service_manage set to "false" so the cluster can manage it. I added a notify{} before $service_manage if statement and one one host it is "false" and another has it as the default "true". I can't find where it is being set to "false". I've confirmed it is being set in the host's catalog (not cached in the puppet client). Places I've looked: grep -ir service_manage /etc/puppetlabs/* (includes modules and hiera) foreman node parameters via the web foreman database parameters table Any idea where else to look? I wonder if the upgrades kept an old setting somewhere? I want to fix the old host, but not at the expense of the working one!

@rmeden you want to use "puppet lookup" on the puppetserver to check for hiera values

@Leon Ross has left the channel

Hello, i have a strange situation. I have Puppet sever open source 7 and i have RHEL 9 virtual machine (VM). On this VM i installed Puppet agent and it was working fine. Then this VM was moved to another network and its hostname was changed. Now when i logged into this VM, it's new hostname is "a-dfweq-pgk-001". I went to Puppet server and checked - there is no certificate for this hostname. Then i returned to client VM and stopped puppet service and removed /etc/puppetlabs/puppet/ssl directory completely and after that i executed "puppet agent -t". Usually it should make a new CSR and contact Puppet server to auto sign certificate. But right now i have next error:

a-dfweq-pgk-001 /etc/puppetlabs/puppet # puppet agent -t
Error: Connection to <https://d-dfweq-vua-011.example.com:8140/puppet-ca/v1> failed, trying next route: Request to <https://d-dfweq-vua-011.example.com:8140/puppet-ca/v1> failed after 0.005 seconds: Connection reset by peer - SSL_connect
Wrapped exception:
Connection reset by peer - SSL_connect
Error: No more routes to ca
Error: No more routes to ca

I can see that puppet agent didn't created certificates:

a-dfweq-pgk-001 /etc/puppetlabs/puppet # tree ssl
ssl
├── certificate_requests
├── certs
├── private
├── private_keys
└── public_keys

What interesting when i check on the client VM nslookup, ping, and nc -vz d-dfweq-vua-011.example.com 8140 everything is ok. I even checked tcpdump on Puppet server -> traffic is going ok in both directions. Also i checked SELinux, restarted puppetserver service, checked puppet.conf on client VM. Could you please help me to fix this issue? (also i was using ChatGPT to troubleshoot it, followed all suggestions and it is still not resolved)

Something terminates your connection. Maybe a firewall, load balancer, or http proxy