All of cloud vps is being upgraded to puppet7 with new puppet infra. Each puppetmaster needs to be replaced with a version 7 puppetmaster, and then VMs upgraded to puppet7.
Your project contains the following v5 puppetmaster:
gitlab-runners-puppetmaster-01.gitlab-runners.eqiad1.wikimedia.cloud
Please take a moment to consider whether or not you stlil need this project puppetmaster. If you do, migrate with the following steps:
In order to migrate:
0) Make sure you have available quota to create a new g3.cores1.ram2.disk20 VM. If you need more space please [[ https://phabricator.wikimedia.org/project/view/2880/ | open a quota ticket ]].
1) Create a 5GB cinder volume (named <projectname>-puppetserver or similar) and mount it as /srv on the existing puppetmaster. Them on the existing puppetmaster:
```
$ sudo cp -a /var/lib/git /srv
$ sudo cp -a /var/lib/puppet /srv
```
2) Unmount and detach the cinder volume
3) Create a new VM for the v7 puppet server, using a flavor with at least 2GB of RAM and Debian Bookworm
4) Mount the previously-created cinder volume at /srv on the new server
5) Make the new VM a puppetserver by following directions at https://wikitech.wikimedia.org/wiki/Help:Project_puppetserver#Step_1:_Setup_a_puppetserver.
Puppet classes:
```
role::puppetserver::cloud_vps_project
```
hiera:
```
profile::puppet::agent::force_puppet7: true
puppetmaster: puppet
```
6) Adjust ownership on the new puppetserver:
```
$ sudo chown -R gitpuppet /srv/git; chgrp -R gitpuppet /srv/git
$ sudo chgrp -R puppet /srv/puppet; chgrp -R puppet /srv/git
$ sudo systemctl restart puppetserver
```
7) Assuming that puppet is now running cleanly on the new puppetserver, move existing VMs to the new host with the hiera setting
```puppetmaster: <new puppetserver fqdn>```
8) Finally, update clients of the new puppetserver with the hiera setting
```profile::puppet::agent::force_puppet7: true```
Debian Buster hosts will complain about not being able to install puppet7 but the warning is harmless for now.