storage1.staging: Full-upgrade to bullseye

As this node is now rancher node agent whose purpose is to run the staging objstorage (through rancher). There is no longer any swh services running on this node [1]

This can be upgraded to bullseye (following a similar plan as [2])

• (missed) Drain pods from storage1 node
• Adapt /etc/apt/* files accordingly for bullseye
• /etc git commit
• upgrade
• dist-upgrade
• reboot
• checks dynamic services are getting back up (it is but it's slow as storage1 is slow)

[1] #5164 (closed)

[2] swh/meta#3761 (closed)

task=swh/infra/sysadm-environment#5181
puppet agent --disable "$task: dist-upgrade to bullseye"
cd /etc
sed -i -e 's/buster/bullseye/' /etc/apt/sources.list.d/*
sed -i -e 's,bullseye/updates,bullseye-security,' /etc/apt/sources.list.d/debian-security.list
git status
git diff
grep bullseye-security /etc/apt/sources.list.d/debian-security.list
git add .
git commit -m "$task: Migrate sources.list to bullseye"
apt update
apt upgrade -y
apt dist-upgrade -y
reboot

changed milestone to %MRO 2023

added activity::MRO label

mentioned in issue #5164 (closed)

changed title from storage1.staging: Full-upgrade to next debian stable to storage1.staging: Full-upgrade to bullseye

changed the description

changed the description

changed the description

marked the checklist item checks dynamic services are getting back up (it is but it's slow as storage1 is slow) as completed

It went ok.

One mishap to note though, the pods should have been drained first prior to actually reboot. So the time of restart of the pods would have been shorter than it was.

The pods would have been moved to other cluster nodes. The only pod which would have crashed anyway is the objstorage (since it absolutely needs the volume mount present only in storage1).

changed the description

closed