Given that we can't enroll new Puppet 5 clients on the Puppet 7 infra and Buster doesn't have Puppet 7 available, let's disable the creation of new Buster VMs.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Andrew | T351450 Migrate Cloud VPS puppet infrastructure to Puppet 7 | |||
| Resolved | Andrew | T331738 Cloud-vps Buster deprecation | |||
| Resolved | taavi | T351499 Restrict creation of new Debian Buster VMs |
Event Timeline
Comment Actions
Toolforge might still need new Buster-based k8s workers until I get them running on Bookworm. So, following https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/VM_images#Restricted_images, I did this:
taavi@cloudcontrol1007 ~ $ sudo wmcs-openstack image set --property visibility=shared --project tools 261865bc-7ed5-4df0-be08-80657a388514 taavi@cloudcontrol1007 ~ $ sudo wmcs-openstack image set --activate 261865bc-7ed5-4df0-be08-80657a388514 root@cloudcontrol1007:~# glance member-create 261865bc-7ed5-4df0-be08-80657a388514 observer +--------------------------------------+-----------+---------+ | Image ID | Member ID | Status | +--------------------------------------+-----------+---------+ | 261865bc-7ed5-4df0-be08-80657a388514 | observer | pending | +--------------------------------------+-----------+---------+ root@cloudcontrol1007:~# glance member-update 261865bc-7ed5-4df0-be08-80657a388514 observer accepted +--------------------------------------+-----------+----------+ | Image ID | Member ID | Status | +--------------------------------------+-----------+----------+ | 261865bc-7ed5-4df0-be08-80657a388514 | observer | accepted | +--------------------------------------+-----------+----------+