I think this would've been done yesterday by Reception123, so just needs a reboot on servers that weren't rebooted. Some major ones had to be because of outage. db* was rebooted, mon111 was rebooted, phab121 was rebooted, a single mw server was (by me) and test101 was. So I think all those are already done.
But I would like to note, for the record upgrades should never be done like the way they were this time, and should be done with unattended-upgrades, and never with apt upgrade on all servers at once, at least not without scheduling downtime. But because of it those servers would've already had the kernel upgraded. I can do the rest of the MediaWiki servers today though (mw*, mwtask111, and jobchron121)
The best bet in my opinion is the reboot them during the MW upgrade as users already expect broken.
@Paladox is this something you can facilitate?
Sure. Although note that proxmox uses a different kernel (a customised one).
We could also use that window to upgrade proxmox? (https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_7.2)
Each vm would need to be stopped so that we make sure there is no corruption. Also they would manually have to be started after rebooting the cloud server.