cumin1001.eqiad.wmnet is already running on Bullseye. In theory the deployment-cumin host would've been rebuilt with Bullseye before that happened, but maybe this is a good time to skip ahead and test things on Bookworm.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Andrew | T327742 Migrate deployment-prep away from Debian Buster to Bullseye/Bookworm | |||
| Resolved | jhathaway | T361380 Replace deployment-cumin with Bullseye or Bookworm host |
Event Timeline
Comment Actions
@jhathaway, assigning to you because I think you built the latest production cumin hosts. Feel free to reassign as appropriate.
Comment Actions
Upgrade the VM with dist-upgrade.sh and rebooted. Do we need to do anything to update the OS metadata in Horizon?
Comment Actions
I don't know of useful thing to do with metatdata here since the OS is derived from the original base image (which hasn't changed). We will just try to remember not to nag for these hosts that were upgraded in place. More pets and less cattle :(