It looks like the SnakeYAML library does have

setCodePointLimit

and

setNestingDepthLimit

methods --- but those are not exposed at the JRuby level yet: https://github.com/jruby/jruby/issues/7543 So, the limits are fixed to the SnakeYAML defaults of 3 MB for size and 50 for nesting depth.

This message was deleted.

same deal with plans doc

The docs in question I found that refer to the issue are here https://developer.hashicorp.com/vault/docs/auth/cert There's a note in there about unique serials

I am still monitoring this and I will chase when I get back from leave as I know others have hit this when doing upgrades

Has anyone seen an issue like this before, trying to upgrade an agent.. but we get a lovely error message regarding GPG keys. So far we have moved existing keys to allow the module to replace the keys yet they still don't work. Could it be the module version / age contains old keys?

Do you use puppetlabs/puppet_agent to manage agents ?

Yes

hmm, it should have updated new gpg keys

Would it still have them in version 2.0.1?

which version of puppetlabs/puppet_agent? 😄

we are upgrading some pretty old code..

that's ....ancient

that's ....ancient

the new gpg key is from 2020? and 2.0.1 is from 2019

I did think we need to push to update all code and use a later version of the module..

Thankyou! felt like i was going mad

Just to confirm that was exactly the issue.

This message was deleted.

This message was deleted.

This message was deleted.

Good day I'm struggling to determine why our testbed PE server is unable to refresh the list of class definitions it should have from our set of dev environments... The console shows an error stating "Error retrieving class definitions" The logs aren't very clear about the what's happening at the time when I click on the "Refresh" link to update the class definitions... I can't find anything in the Puppet Server logfiles at /var/log/puppetlabs/puppetserver/puppetserver.log or /var/log/puppetlabs/orchestration-services/orchestration-services.log The only thing related I can find is in the Console Services logfile at /var/log/puppetlabs/console-services/console-services.log where the entries look like this: === INFO [p.c.class-updater] Requesting classes in development from https://puppetserver:8140/puppet/v3/environment_classes?environment=development with etag e87750971897e8a55a651f3afb01880efc537b9637fa46f1c6f1c6aa09a352c9 INFO [p.c.class-updater] 304 response received for request for classes in development. === Any ideas on what to look for would be greatly appreciated... Thanks

@jonathan.newman / @steveax I found that for node groups with no rules, i.e., <https://www.puppet.com/docs/pe/2021.7/groups_endpoint.html#get-v1-groups-id-rules%7CGET /v1/groups/<id>/rules> returns

null

in the

rule

key, the translated rules are returned as

[ "=", "node_state", "active" ]

, which matches all nodes, exactly the opposite of what is shown in the PE Console under "Matching nodes". Is this a bug in the API?

This message was deleted.

This message was deleted.

Am i understanding the file location correctly?

The site-modules directory is the equivalent of the modules directory when using the file resource?