This message was deleted.

https://github.com/voxpupuli/puppet-ghostbuster is one way

https://github.com/bastelfreak/env2module-differ something like that

https://github.com/voxpupuli/puppet-catalog_diff our catggalog-differ is the perfect tool to find such problems

This message was deleted.

Newbie PE question... in regard to node licensing. If I have a single server with a PE agent running on the OS and then also want to manage the idrac configuration through some tool like: https://github.com/dell/openmanage-puppet would that burn 2 PE licenses?

This message was deleted.

Yes so assuming the node you had been using previously is going away, the only thing you need to do is remove all the metrics dashboard classficiations and hiera/enc mentions. The operational dashboards consumes the some of the same dependancies, so will take over managing some of those on the puppetserver nodes, it should be relativly seamless

This message was deleted.

This message was deleted.

This message was deleted.

I have a weird situation. I'm running puppet enterprise, using code deploy with ssh transport to a local git repo. I upgraded my RHEL 7 server to puppet enterprise 2021.7.0.16 a while ago and everything was great except code deploy failed with a core dump due to memory corruption in libssh2. While I have a valid license, it is through our central IT group, and I have to go through them to open a ticket, and long story short I could never get a ticket working for various reasons. I found I could simply copy the system libssh2 libraries into /opt/puppetlabs/server/apps/r10k/lib/ and everything was working fine, and I've not had any problems with that server since. So now I've tried to upgrade my Ubuntu 20.04 server to puppet enterprise 2021.7.1.10 and I've run into the same problem. Copying the system libssh2 libraries doesn't fix it this time (no change). Copying the system libssh2 and libgit2 gets further, but gives another error due to the version of libgcrypt they use. I'm at a standstill on how to fix this, other than I can get it to run (very slowly) by running it in valgrind, but this isn't practical solution. I'm beginning to think since this has happened on two disparate systems now, that it maybe isn't puppet or libssh2 so much as something else specific to my environment (the ssh key used, or the git server's ssh configuration, the git-shell I've implemented there, etc). So, my questions are: Has anyone seen anything like this before? Any ideas on why this is happening? Any solution? Any debugging tips?

Update: I compiled the libssh2 simple example programs ssh2_exec and ssh2 and ran them against both the system libssh2 and the puppet enterprise libssh2 libraries. Both programs work with the system libssh2 library. While ssh2_exec works with the puppet libssh2 library, the ssh2 program fails with the puppet libssh2 library. So, at least I have some way to reproduce/test/debug outside of puppet enterprise now. Oddly, while I thought it would fail with the public key auth, it also fails with password auth... The mystery continues.

This message was deleted.

@nigel has left the channel

@April Murphy has left the channel

@greglarkin has left the channel

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

I, for one, welcome our new PE 2023.0 and 2021.7.2 releases. But also I am sad to see that wether ubuntu 22 nor RHEL/CentOS 9 has made it into the release. But CentOS 8 was dropped 🤔 and no Streams 8 Support added. I'm happy, but confused.

This message was deleted.

This message was deleted.

you can stop the puppet agent and edit the java args in /etc/sysconfig/pe-puppetdb (on rhel systems)

message has been deleted

This message was deleted.

This message was deleted.

I have no clue what

support_tasks::st0317b_purge_node

is, but if the new node using a different certificate and you don't allow duplicate, you will need to clean the certificate on server and node and regenerate, or just copy the old one from the old one if you have them.