Project

General

Profile

Actions

action #161111

closed

coordination #151816: [epic] Handle openQA fixes and job group setup

To trace whether SLEM 5.2 MU patch 33772 and SLEM 5.3 MU patch 33773 released

Added by zoecao about 2 months ago. Updated 19 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
Start date:
2024-05-29
Due date:
% Done:

0%

Estimated time:

Description

Motivation

This ticket is to trace whether both of the [SLEM 5.2 MU patch 33772] and [SLEM 5.3 MU patch 33773] released. If they are released, need to revert this [PR].

Acceptance criteria

AC1 : Check if [SLEM 5.2 MU patch 33772] and [SLEM 5.3 MU patch 33773] are released
AC2 : Revert this [PR].
AC3 : Clone the latest job of slem_migration_5.2_to_5.3 to see whether any new issues.

Actions #1

Updated by zoecao about 2 months ago

  • Description updated (diff)
Actions #2

Updated by zoecao about 2 months ago

I submit PR to revert the workaround PR: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/19421

The patches are both released:
https://smelt.suse.de/incident/33772/
https://smelt.suse.de/incident/33773/
And the case slem_migration_5.2_to_5.3 pass in latest run(wicked.server is active after migration): https://openqa.suse.de/tests/14482436#step/zypper_migration/33
Besides the added workaround PR caused new issues on [slem_migration_5.3_to_5.4] and [slem_migration_5.4_to_5.5] jobs, I verified that if removing the workaround, they could pass:
https://openqa.suse.de/tests/14485759#step/zypper_migration/31 (slem5.3 to slem5.4 migration without PR#19403)
https://openqa.suse.de/tests/14485760#step/zypper_migration/31 (slem5.4 to slem5.5 migration without PR#19403)

Actions #3

Updated by JERiveraMoya 19 days ago

  • Tags set to qe-yam-jun-sprint
  • Status changed from New to Resolved
  • Assignee set to zoecao
  • Parent task set to #151816
Actions

Also available in: Atom PDF