Thanks for the followup in IRC. We are migrating the service to the Prod VPS in the next week. After that, I'll determine if we still need this puppetserver for testing. If we do, I will follow the instructions to migrate, otherwise I will destroy the host and we will use the standard puppetserver.

I've built a new puppetserver in this project, wdqspuppetserver-1. Nothing was using the old one so probably this effort was in vain.

puppetserver is upgraded but everything in this project is Buster so puppet 7 will be unhappy until that's fixed.

This project was managed by jbond -- for now I will do this upgrade.

10:28 AM taavi, jhathaway, moritzm, is the puppet-dev project effectively defunct now that jbond has departed? It's unmarked on the purge page and also has https://phabricator.wikimedia.org/T361593 with no response
10:29 AM
<moritzm> Moritz Mühlenhoff let me have a look
10:31 AM I haven't used it for ages and I think it was mostly used to stage/test the puppet 7. from my PoV it can be phased out unless Jesse or Taavi still use it
10:32 AM <andrewbogott> Andrew Bogott ok, thanks moritzm, let's see if anyone else has an opinion :)
10:34 AM
<jhathaway> Jesse Hathaway I agree with moritzm, I would like to keep the project around, but the instances can be removed
10:35 AM <andrewbogott> Andrew Bogott great, shall I delete things right now?
10:37 AM
<jhathaway> Jesse Hathaway fine by me, unless taavi objects
10:37 AM
<jbond> John Bond ftw also good with me
10:37 AM
<taavi> Taavi Väänänen no objections from me

Change #1019109 merged by Dzahn:

[operations/puppet@production] cloud/devtools: switch default puppetmaster from 1001 to 1003

https://gerrit.wikimedia.org/r/1019109

Change #1019109 had a related patch set uploaded (by Dzahn; author: Dzahn):

[operations/puppet@production] cloud/devtools: switch default puppetmaster from 1001 to 1003

https://gerrit.wikimedia.org/r/1019109

I changed puppetmaster-1003 to role::puppetserver::cloud_vps_project, and puppet runs now seem to be working there. @Dzahn is updating other boxen in the project to use the new puppetmaster. We'll consider this one resolved.

Mentioned in SAL (#wikimedia-cloud) [2024-04-11T18:23:00Z] <mutante> - shutting down puppetmaster-1001 on buster - should now be replaced by puppetmaster-1003 on bookworm (thanks brennen) T360964 T360470

In T360470#9685143, @Dzahn wrote:

Error 500 on SERVER: Server Error: Could not find class role::puppetserver::standalone for puppetmaster-1003.devtools.eqiad1.wikimedia.cloud on node puppetmaster-1003.devtools.eqiad1.wikimedia.cloud

I'm not sure this is the cause of the problem, but is there any reason to have your new puppetserver manage itself rather than use the central puppetserver? My instructions up top say to add the hiera 'puppetmaster: puppet' which would avoid weird chicken/egg issues.

The new puppetserver looks fine. I un-registered one runner (runner-1026.gitlab-runners.eqiad1.wikimedia.cloud) and re-registered and it looks good. Also the private profile::gitlab::runner::token is correct.

We don't have any more unmerged puppet patches AFAIK. For the newer upgrade, we should have some.