action #111989
Updated by tinita almost 2 years ago
## Motivation Seems like o3 machines do not automatically reboot anymore, likely because we continuously call `zypper dup` so that the nightly upgrades don't find any changes? See #111758#note-18 ## Acceptance criteria * **AC1:** O3 machines are rebooted after updates requiring a reboot * **AC2:** Eventually root filesystem snapshots are cleaned up ## Suggestions * Monitor machines for some weeks to keep track of updates * Check that there's no pending kernel update, can be done with `for i in openqaworker1 openqaworker4 openqaworker7 imagetester rebel power8; do ssh root@$i "zypper ps | tail -n 2"; done` * Revisit the update logic to only upgrade openQA packages instead of everything. We discussed this and came to the conclusion that we created an ugly Frankenstein-Monster which nobody should do. Yet another confirmation that the proper way(s) to go are either a fully rolling distribution, aka. Tumbleweed, or transactional-update server + container with continuously deployed workload on top