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

[operations/puppet@production] set target quarter for miscweb bullseye upgrade to 2023-1

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

Change 900463 merged by Dzahn:

[operations/puppet@production] set target quarter for miscweb bullseye upgrade to 2023-1

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

miscweb1002 removed - buster hosts -1

gerrit1001 has been destroyed today

planet1002/planet2002 - deleted, replaced with bookworm VMs

@Muehlenhoff Where does deploy* (deployment_server role both prod and wmcs) fit in? Since we are still on buster there. But want bullseye deployment_servers in cloud VPS projects and production hasn't upgraded the role yet. A legit subtask for here?

In T291916#9742764, @Dzahn wrote:

@Muehlenhoff Where does deploy* (deployment_server role both prod and wmcs) fit in? Since we are still on buster there. But want bullseye deployment_servers in cloud VPS projects and production hasn't upgraded the role yet. A legit subtask for here?

These huge meta tasks are not erally useful, they only end up causing avalances of notifications for little gain. The list of OS updates is being tracked by https://os-reports.wikimedia.org/buster.html (under team breakdown)

Ok, fair enough about the tracking task. But don't we still need some kind of task that someone can take to do the actual upgrade work? So all the subtasks without the tracking parent task?

In T291916#9744868, @Dzahn wrote:

Ok, fair enough about the tracking task. But don't we still need some kind of task that someone can take to do the actual upgrade work? So all the subtasks without the tracking parent task?

Sure, a task for the actual update of the deployment servers makes perfect sense!