Page MenuHomePhabricator

Rebuild integration-agent-pkgbuilder-1001 and integration-agent-pkgbuilder-1002 to get rid of Debian Buster
Closed, ResolvedPublic

Description

The instances are used to run the Debian package builder maintained in Puppet.

The instances:

integration-agent-pkgbuilder-1001.integration.eqiad1.wikimedia.cloud bd31b30d-ab6b-4945-8ade-22268a34e6a2 172.16.0.71 g2.cores2.ram4.disk40 Debian Buster
https://openstack-browser.toolforge.org/server/integration-agent-pkgbuilder-1001.integration.eqiad1.wikimedia.cloud

integration-agent-pkgbuilder-1002.integration.eqiad1.wikimedia.cloud 5c6c835c-4b45-4d0b-91ac-445fbab12a81 172.16.0.122 g2.cores2.ram4.disk40 Debian Buster
https://openstack-browser.toolforge.org/server/integration-agent-pkgbuilder-1002.integration.eqiad1.wikimedia.cloud

Puppet classes

profile::openstack::eqiad1::cumin::target
role::ci::slave::package_builder

Hiera settings

profile::ci::docker::docker_version: 5:20.10.18~3-0~debian
profile::java::java_packages: [{'variant': 'jre-headless', 'version': '11'}]
profile::openstack::eqiad1::cumin::project_masters: ['172.16.1.230']
profile::openstack::eqiad1::cumin::project_pub_key: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIPPfdabE1Fej0X86QgjY72LXvA3Wawrg0ZcDL0PF56/A root@integration-cumin
puppetmaster: integration-puppetmaster-02.integration.eqiad.wmflabs

Event Timeline

They should be straightforward to rebuild thanks to Puppet. I don't know whether we should target Bullseye or Bookworm, it would best if we aligned with whatever is used by the production host build2001.codfw.wmnet. I can sync with Moritz to get some details, beside that I am not worried about rebuilding them.

There's nothing particularly OS-specific for the builder role, I'd suggest to directly go to Bookworm.

I will rebuild them tomorrow as well as integration-cumin ( T360784 ). That should be straightforward given production has already migrated and that the systems are fully puppetized.

I will recreate them using Bullseye which is what is used in production.

I have already deleted integration-agent-pkgbuilder-1001 but could not recreate one since the old instances had the flavor g2.cores2.ram4.disk40 and there is no similar flavor available. I need a new flavor to be created.

Mentioned in SAL (#wikimedia-releng) [2024-07-17T16:36:17Z] <hashar> Created integration-agent-pkgbuilder-1003 to replace EOL Buster instances # T360786

Mentioned in SAL (#wikimedia-releng) [2024-07-18T08:26:22Z] <hashar> Deleted Buster based integration-agent-pkgbuilder-1001 integration-agent-pkgbuilder-1002 , replaced them with Bullseye based integration-agent-pkgbuilder-1003 and integration-agent-pkgbuilder-1004 # T360786

I have build the two instances using Bullseye as a base image and added them as Jenkins agents.

Should we delete the old ones to close this out?

Should we delete the old ones to close this out?

integration-agent-pkgbuilder-1001 and integration-agent-pkgbuilder-1002 were gone, maybe they were still around at the time you made your comment since there was a blocker upon T370337 ;)