Have you tried logging in as "admin"? Unintuitively, that is the default root username.

no letme try that

I'm in thank you

Is servicenow integration still a thing with CD?

Anyone know what this means? Module pwshlib failed to synchronize due to PuppetForge:V3Release:ChecksumMismatch

For like the last couple years the control-repo is missing in the pipeline yaml code generated on the 'Manage as code' page

Any sort of podman support on Windows for the job hardware?

I think I know the answer but thought it wouldn't hurt to ask

Question about Self Signed Certs and CD4PE V5. I'm trying to understand about the cert associated with the CD4PE server and Website. This is a server which has a puppet agent on it where that agent cert is a trusted cert. But the cert associated with CD4PE webui shows two certs... a CA and a cert both associated with the server name (cdp001 in this case). Is my only option of not having a self signed cert to to trust this newly generated CA and cert....or if I upload the ca.pem from the agent which is a chain of the cd4pe server and the trusted Puppet signing cert, will that make the cert with CD4PE WebUI non self signed? Bottom line, I have a Security Vulnerability which does not allow the cert for CD4PE to be self signed. I'm looking for guidance on steps to follow... Is it as simple as using the advanced instructions for TLS Certificates? Or is a combination of everything?

@choffee has left the channel

Anyone else have issues with CD 5.x and new license keys?

@CVQuesty has left the channel

Anyone seen this before? Trying to modify / remove a stage and this error pops up

Just got out new license for Puppet Advanced,,,, Does uploading it to PE cover the associated CD4PE or do I need to run the bolt plan to upload the license to CD4PE? We currently don't have any pipelines which use Impact Analysis... if that helps the answer.

CD doesn't need the license, but IA does. I would go ahead and upload the license, just in case you decide you want to use IA. But, CD will work without it.

I guess I should be a little more clear... you need the license on the CD server in order to use IA. The license on the PE server does nothing except license PE itself, and tell you whether you are licensed for the other advanced features.

GM... Any news about when the next version of CD4PE will be available? Just doing some planning.. and realized one had not been released since Jan.

There is a release of both 4.x and 5.x scheduled for mid-April.

We are now on a quarterly schedule for planned releases.

Finally, we managed to complete the migration and upgrade for CD4PE 4.27.1 to v5.7. It was great learning with challenging outcomes when setting it up on an Airgapped environment.

So General Question... Standing up a new instance of CD4PE attached to a new instance of Puppet. CD4PE is v5.8 and Puppet is at 2025.2. When I try to configure either using a Token or manually configure the integration between CD4PE and Puppet, immediately I get the Red Box with "An error occurred: Please contact an Administrator" which is kind of ironic since I am the Admin... but anyways... Where can I look to find out what's wrong and what I can do to resolve such an issue. I have already verified that ports are open.

CD4PE V5.8 running on an Azure VM... there is no way to update the resolv.conf or /etc/hosts because of the Podman CNI backend... which is outdated. Anyone run into this and have a plan for adding a new DNS server to allow us to resolve our ldap server or PE server?

When impact analysis is ran, is it the primaries making the calls out to the forge or is it cd4pe?

Or both

Question .. My Bolt runner server has Internet access but I my Worker node does not. If I all I want to do grab the cd4pe_jobs module from the Forge API, can I somehow use the Bolt Runner as a proxy?

Pretty sure Impact Analysis is just a feature to block me from deploying code at this point. When it decides to fail its a couple nodes that it can't fetch info from PuppetDB for.

Hey... if there is no Data showing up on the Nodes Page of CD4PE... meaning it cannot find the # of nodes with a specific aio_agent_version.,.. What should I look into? Or is this a failure of of mixed versions... like having PE 2025.2 with CD4PE v5.8?

Why does PDK validate give different output in CD4PE than when I run it on my machine? Seems like spacing issues and indents are ignored on my workstation, but once it runs through CD4PE it shows a lot more warnings/errors

I've just kind of ignored it over that last few years... but now other people are complaining

The container CD4PE use is running 3.4 and I'm using 3.4 but seeing different results... I don't get it