bookworm upgrades, third batch: High complexity
upgrade the following servers, if they still exist, one by one, carefully.
-
alberti.torproject.org-bullseye upgrade was #40693 (closed)done in one shot, oops! -
eugeni.torproject.org- bullseye upgrade was #40694 (closed), followup in #41876 (closed) -
hetzner-hel1-01.torproject.org- bullseye upgrade was #40695 (closed) -
pauli.torproject.org- bullseye upgrade was #40696 (closed), puppetdb upgraded separately in #41341 (closed), followup in #41819 (closed) - ganeti servers (#41254 (closed) and #41253 (closed))
Note that some of those machines might not be running bullseye yet, see the related tickets for more information. An upgrade to bullseye MUST be performed first, even if we batch-upgrade them to bookworm, as there are significant issues with skipping the bullseye upgrade. Those were found while accidentally upgrading alberti from buster to bookworm, see #40693 (closed).
In TPA-RFC-57 this also included the ganeti cluster upgrades, but those have been split up in separate tickets (#41254 (closed) and #41253 (closed)).
Designs
- #41252Debian 12 bookworm upgrade
- #41251Debian 12 bookworm upgrade
- #41254Debian 12 bookworm upgrade
- #41253Debian 12 bookworm upgrade
- #41338Debian 12 bookworm upgrade
- #40696Debian 11 bullseye upgrade
- #40695TPA-RFC-33-A: emergency Icinga retirement
- #40694TPA-RFC-71: emergency email deployments, phase B
- #41819Debian 12 bookworm upgrade
- #41876Debian 12 bookworm upgrade
Activity
marked this issue as related to #41252 (closed)
marked this issue as related to #41251 (closed)
marked this issue as related to #41254 (closed)
marked this issue as related to #41253 (closed)
changed milestone to %Debian 12 bookworm upgrade
marked the checklist item
alberti.torproject.org- bullseye upgrade was #40693 (closed) as completedmentioned in commit wiki-replica@6e2f471b
mentioned in issue #41176 (closed)
marked this issue as related to #41338 (closed)
mentioned in issue #41338 (closed)
marked this issue as related to #40696 (closed)
mentioned in issue #40696 (closed)
marked this issue as related to #41353 (closed)
mentioned in issue #41353 (closed)
mentioned in issue #41357 (closed)
marked this issue as related to #41357 (closed)
marked this issue as related to #41411 (closed)
second batch (#41252 (closed)) was postponed to january, so it makes sense to me to push this back to one month later as well.
mentioned in issue #41350 (closed)
mentioned in issue #41252 (closed)
assigned to @lavamind
This issue has been waiting for information two weeks or more. It needs attention. Please take care of this before the end of 2024-05-21. ~"Needs Information" tickets will be moved to the Icebox after that point.
(Any ticket left in Needs Review, Needs Information, Next, or Doing without activity for 14 days gets such notifications. Make a comment describing the current state of this ticket and remove the Stale label to fix this.)
To make the bot ignore this ticket, add the bot-ignore label.
added Stale label
-
postponing so we prioritize bullseye upgrades, in particular #40695 (closed) and #40694 (closed)
Edited by anarcat marked this issue as related to #40695 (closed)
marked this issue as related to #40694 (closed)
marked the checklist item
hetzner-hel1-01.torproject.org- bullseye upgrade was #40695 (closed) as completed-
note for the future: the puppet upgrade is a blocker for prometheus-alerts#20 (comment 3092385)
i also think we should just make an issue about upgrading puppet, since that's basically all that's left here (apart from eugeni).
marked this issue as related to #41819 (closed)
marked this issue as related to #41876 (closed)
mentioned in issue #41876 (closed)
marked the checklist item
eugeni.torproject.org- bullseye upgrade was #40694 (closed), followup in #41876 (closed) as completedmarked the checklist item ganeti servers (#41254 (closed) and #41253 (closed)) as completed