Project

General

Profile

action #99192

coordination #99183: [epic] Upgrade all our infrastructure, e.g. o3+osd workers+webui, to openSUSE Leap 15.3

Upgrade osd workers and openqa-monitor to openSUSE Leap 15.3 size:M

Added by okurz 2 months ago. Updated 12 days ago.

Status:
In Progress
Priority:
Low
Assignee:
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Motivation

  • Need to upgrade workers before EOL of Leap 15.2 and have a consistent environment

Acceptance criteria

  • AC1: all osd worker machines run a clean upgraded openSUSE Leap 15.3 (no failed systemd services, no left over .rpm-new files, etc.)
  • AC2: openqa-monitor runs openSUSE Leap 15.3

Suggestions

Further details

  • Don't worry, everything can be repaired :) If by any chance the worker gets misconfigured there are btrfs snapshots to recover, the IPMI Serial-over-LAN, a reinstall is possible and not hard, there is no important data on the host (it's only an openQA worker) and there are also other machines that can jobs while one host might be down for a little bit longer. And okurz can hold your hand :)

  • for reference the upgrade to openSUSE Leap 15.1 was described #55607


Related issues

Copied from openQA Infrastructure - action #75238: Upgrade osd workers and openqa-monitor to openSUSE Leap 15.2Resolved

History

#1 Updated by okurz 2 months ago

  • Copied from action #75238: Upgrade osd workers and openqa-monitor to openSUSE Leap 15.2 added

#2 Updated by okurz 2 months ago

  • Subject changed from Upgrade osd workers and openqa-monitor to openSUSE Leap 15.2 to Upgrade osd workers and openqa-monitor to openSUSE Leap 15.3
  • Description updated (diff)
  • Assignee deleted (cdywan)
  • Priority changed from High to Normal

#3 Updated by okurz 2 months ago

  • Priority changed from Normal to Low

#4 Updated by mkittler about 2 months ago

  • Subject changed from Upgrade osd workers and openqa-monitor to openSUSE Leap 15.3 to Upgrade osd workers and openqa-monitor to openSUSE Leap 15.3 size:M
  • Status changed from New to Workable

#5 Updated by kodymo 12 days ago

  • Status changed from Workable to In Progress
  • Assignee set to kodymo

#6 Updated by mkittler 12 days ago

On o3 we've noticed problems (see #99189#note-15 and subsequent comments), so I suppose it makes sense to add a lock before upgrading:

zypper al qemu-ovmf-x86_64

A lock for qemu-seabios shouldn't be necessary (as of https://github.com/os-autoinst/os-autoinst/pull/1838).

Also available in: Atom PDF