Hi, Is Puppet Razor dead?

oh yes

This message was deleted.

@woter We're also dismayed at Razor going away, and are looking at either MaaS or Cobbler as a replacement. If you or anyone else has any suggestions, definitely pass them along :)

This message was deleted.

I know RHEL 9 has only recently been generally released, but does anyone know if there is a timeline to support installing PE services on RHEL9 as the primary/replica servers? It looks like there is some Agent support but not yet the main server

This message was deleted.

@Marty Ewings did you ever see

java.lang.StackOverflowError: null

in the puppetserver.log? This seems to happen for different nodes that request a catalog (PE 2019.8.11), but not everytime they request it. sometimes it works

2022-06-13T00:15:07.039+02:00 WARN  [qtp1244214305-133792] [o.e.j.s.HttpChannel] /puppet/v3/catalog/$fqdn
java.lang.StackOverflowError: null
        at opt.puppetlabs.puppet.lib.ruby.vendor_ruby.puppet.pops.types.types.RUBY$method$resolve$0(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:3472)
        at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:106)
        at org.jruby.internal.runtime.methods.MixedModeIRMethod.call(MixedModeIRMethod.java:140)
        at org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:200)
        at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:173)
        at opt.puppetlabs.puppet.lib.ruby.vendor_ruby.puppet.pops.types.types.invokeOther1:resolve(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:2759)
        at opt.puppetlabs.puppet.lib.ruby.vendor_ruby.puppet.pops.types.types.RUBY$method$resolve$0(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:2759)
        at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:106)
        at org.jruby.internal.runtime.methods.MixedModeIRMethod.call(MixedModeIRMethod.java:140)
        at org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:200)
        at org.jruby.runtime.callsite.CachingCallSite.cacheAndCall(CachingCallSite.java:376)
        at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:175)
        at opt.puppetlabs.puppet.lib.ruby.vendor_ruby.puppet.pops.types.types.invokeOther33:resolve(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:3506)
        at opt.puppetlabs.puppet.lib.ruby.vendor_ruby.puppet.pops.types.types.RUBY$method$resolve$0(/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/pops/types/types.rb:3506)
        at org.jruby.internal.runtime.methods.CompiledIRMethod.call(CompiledIRMethod.java:106)
        at org.jruby.internal.runtime.methods.MixedModeIRMethod.call(MixedModeIRMethod.java:140)
        at org.jruby.internal.runtime.methods.DynamicMethod.call(DynamicMethod.java:200)
        at org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:173)

Full trace: https://gist.github.com/bastelfreak/97d689d617fcbd8dcbe8d4ae0de38fb4

how do I group together all the nodes that have their agent disabled? PQL or a fact? I want to re-enable and set to noop

Good old times 🙂

mco find -S "puppet().enabled=false"

I think you need to write a fact

I wonder if it gets uploaded to puppetdb if agent is disabled? never checked that

probably not

if I was using mco

One can write a bolt task to figure out if agent is disabled and you can create a plan that filters based on that

from the console - I don't think it's possible, happy to be wrong

This message was deleted.

Making a puppet fact for whether the agent is disabled seems like a good idea if you have a lot of issues with people disabling the agent.

right, but does disabled agent send facts to PDB ?

right, but does disabled agent send facts to PDB ?

good point you could invoke the

facts submit

command or whatever it is in cron once a day or something to make sure you could catch them

we just have a check in our monitoring system for last_run > 1 day

why do I need to change the digest_algorithm to sha256 after upgrading to pe 2021 from 2019? (filebucket issue)

why do I need to change the digest_algorithm to sha256 after upgrading to pe 2021 from 2019? (filebucket issue)

I think md5 got dropped? (and shouldnt be used since ages)

MD5 is utterly broken and trivial to create collisions for these days. SHA1 is broken enough that collisions can be computed for some expense. SHA256 is now the standard that most things use as a default.

that works also well on puppet 6 and I recommend it using it on PE2019/puppet6 already

This message was deleted.

Just upgraded 2019.8.11 to 2021.6 with no issues. Used the puppet infra commands to upgrade 7 compilers. The process was fa-mazing. Provisioning a replica tomorrow.

Just upgraded 2019.8.11 to 2021.6 with no issues. Used the puppet infra commands to upgrade 7 compilers. The process was fa-mazing. Provisioning a replica tomorrow.