First attempt at upgrading Puppet Enterprise from 2021.7.10 to 2023.8.3 with peadm::upgrade failed over here... any experiences with PIM?

which error did you get?

personally I try to avoid PIM, it just adds an layer of abstraction and I don't see a value in that

I'm just reviewing the installer.log. Prominent message is a classification conflict with differing values for "pe_repo". At least that's something to look for now... bit confusing because there was no change since the last upgrade in terms of that, but well, let's see.

Normally I use the puppet_agent module to deploy new versions of the Puppet Agent after a PE upgrade, but now I need to install the newer version of the Puppet agent that didn't come bundled with PE. Anyone have any suggestions on how to do that or if I can get the puppet_agent module to still do it for me?

add forge version to modulepath before /opt/puppetlabs/puppet/modules and it will be used

I don't think puppet_agent comes with PE though

I don't need to update the module, I need to update the agent

despite the fact I did say module before... oops

I need to go back to bed apparently lol

ah. I still used puppet_agent to update Fedora, for example, which is not supported promptly. you just have to set hiera properly

For example,

puppet_agent::manage_repo: false
 yum::repos:
   puppet:
     descr: 'Puppet 7 Fedora 40 Repository'
     baseurl: '<http://yum.puppet.com/puppet7/fedora/40/x86_64>'

Right now our agents all point at the primary to download the agents... also I have to do this update on Windows

can't say anything for windows, but I imagine something similar

I set the agent_version param in the pe_repo::windows_x86_64 class and it appeared to download a new version, now just need to see what happens if I try deploying

Does anyone know what User ID and PWD I need to use to download Puppet Agents? We have a few clients who are trying out AIX... but for the first time... When I went to download the agent it asked for a User ID and Pwd?

AIX is limited to Puppet Enterprise. They will need to set up downloads using their license key and following the instructions in the Puppet Enterprise documentation.

I had heard rumors someone built it with a copy of a combo of IBM C and the GNU toolkits for AIX (lives in /opt/freeware if you can believe it)

Sorry in advance already if this is redundant - honestly not sure whether there was already some talk about it - but: is there a way to make this... r10k abstraction layer, Code Manager, clean up branches that vanished from the code repository?

that should happen on each code deploy

OK so I'll guess I'll push some new branch for ther sake of deploying for now and see what happens. (edit: ...using a webhook from GitLab)

Ah, seems like a bit of confusion on my side, a ...bin/puppet code deploy also still does the trick. Sorry :D

The web hook did not trigger cleanup, and Code Manager documentation states that Code Manager does not allow for manual code deploys... guess I got lost there somewhere. Time for investigating the former and maybe for a time of... transition... set up a systemd timer fwiw

shouldn't make a difference if you trigger code deploy via the webhook or

puppet code deploy

in both cases code-manager should purge unknown environments. the purge level can also be configured

Point 1: GitLab wasn't configure to employ the webhook on a tag push event. Branch deletion does not exist as event, so there's that. A test deleting one branch and pushing a fresh other now resulted in deletion and creation inside Code Manager as well, within a minute. That was at least slower before, but all in all Code Manager still does what it has to.

btw, code manager doesn't handle deleted branch event properly, throughs a stack dump in server's log

👋 We're in the process to update from 2023.2.0 to 2023.8.3 and after running the update, the agent run fails on this:

Error: Could not retrieve catalog from remote server: Request to <https://pe-primary.xxxx:8140/puppet/v3/catalog/pe-primary.xxxx?environment=production> failed after 59.078 seconds: SSL_read: unexpected eof while reading
Wrapped exception:
SSL_read: unexpected eof while reading
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

I have a case with support ongoing but if anyone saw this in the past ... 🙂

When following the docs https://help.puppet.com/pdk/current/topics/install_pdk_apt.htm i get the following error

The repository '<https://apt-puppetcore.puppet.com> noble Release' does not have a Release file.

this is with successful authentication.

<https://apt-puppetcore.puppet.com/dists/noble/>

also throws a 404. I was hoping for at least a directory listing but no luck

as far as I know, you must authenticate to access the repos. puppet core is no longer open source.