well, that doesn't happen during catalog compile, it fails to deploy an environment

I'll open a PE ticket ¯\_(ツ)_/¯

You can run the following to get more detailed code deploy logging runuser -u pe-puppet -- /opt/puppetlabs/puppet/bin/r10k -c /opt/puppetlabs/server/data/code-manager/r10k.yaml deploy environment ITTO_4954_gdc --puppetfile --verbose debug2

You can run the following to get more detailed code deploy logging runuser -u pe-puppet -- /opt/puppetlabs/puppet/bin/r10k -c /opt/puppetlabs/server/data/code-manager/r10k.yaml deploy environment ITTO_4954_gdc --puppetfile --verbose debug2

same deal, not much more data

This message was deleted.

what’s weird is now I looked for that error and it seems like it really should be related to pool_size https://github.com/puppetlabs/r10k/blob/dccc3799224d39b03e35c474936b53224285ad3f/lib/r10k/content_synchronizer.rb#L46

it just happened at that line of code

I am looking at this now and the problem is that

libgit2

thinks that the branch name is an OID due to the format.

libgit2

is parsing the branch name to identify what the

ref

is. It starts by looking at the string to see if it is hex, which could be a OID. The OID is too short as the min length is [4 characters](https://github.com/libgit2/libgit2/blob/main/include/git2/oid.h#L30) . It then sends the error [here](https://github.com/libgit2/libgit2/blob/main/src/libgit2/object.c#L187-L190).

This message was deleted.

This message was deleted.

@bastelfreak In order to facilitate the transition, we are going to keep running the legacy networking infrastructure to connect to the Forge until 6/4/22. To use this network path, you can add a private DNS record pointing forge.puppet.com to 192.69.65.71

Hi everyone. Using PE 2021.4, was trying out the Patch Management functionality

It has been running for a bit, with all the patch groups defined, etc

then added some changes to the patch groups, added some, changed some rules on a couple

on the Patch Management, can’t see the groups. The fact patch_group under pe_patch shows “” for all the nodes

On the classification I can see nodes show up in every group, under Matching nodes: nodes match the rules for this node group

tried to change patch_management to absent, then enabled it again, still no luck

tried to change patch_management to absent, then enabled it again, still no luck

on the Patch Management, can’t see the groups. The fact patch_group under pe_patch shows “” for all the nodes

This message was deleted.

This message was deleted.

What is the best way to migrate nodes from different PE versions where unique CA certs were used?

Just checked and the nodes are showing up

https://github.com/fervidus/puppet_ca_utils Might help it can set up mutal trust between cas

This message was deleted.

Hey people. I'm using https://github.com/puppetlabs/puppetlabs-satellite_pe_tools . the lib/ directory got pluginsynced. after updating the routes.yaml to use satellite as indirector and restarting pe-puppetserver I get

could not find terminus satellite for indirection facts

. Anyone has an idea what's wrong/missing? I'm on PE 2019.5

Hey people. I'm using https://github.com/puppetlabs/puppetlabs-satellite_pe_tools . the lib/ directory got pluginsynced. after updating the routes.yaml to use satellite as indirector and restarting pe-puppetserver I get

could not find terminus satellite for indirection facts

. Anyone has an idea what's wrong/missing? I'm on PE 2019.5

did you restart puppetserver after installing report ?