Project

General

Profile

Actions

action #91554

open

[qem][leap][opensuse][qe-core] Update GM images before running upgrade tests

Added by mgrifalconi almost 3 years ago. Updated 8 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
Category:
Enhancement to existing tests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Problem
On Leap, but possibly in other versions as well, we are using some old fixed GM images to run upgrade tests.
Example here https://openqa.opensuse.org/tests/1702657#settings

For example upgrade_Leap_15.2_gnome etc at https://openqa.opensuse.org/tests/overview?distri=opensuse&version=15.4&build=167.2&groupid=50

Reasoning
It would be common sense to migrate an updated system and not a very old one. We should consider updating the image before running the migration test.

Additional info
Conversation here https://chat.suse.de/channel/qe-core?msg=F9jaJXj4DmPxqeRJ4

See also comments at https://progress.opensuse.org/issues/107965

Acceptance Criteria

AC1: Before running migration tests, apply all updates. Use an old image as the beginning, therefore both testing updating all updates and a distribution version update (migration).


Related issues 7 (2 open5 closed)

Related to openQA Tests - action #89263: [leap 15.3][qe-core] Please add migration testing from 15.2 to 15.3 and remove migration tests from 42.XResolvedmgrifalconi2021-03-01

Actions
Related to qe-yam - action #97487: Optimize installation of incident repos in SLE maintenance full testsRejected2021-08-25

Actions
Related to openQA Tests - action #97484: [qe-core] Use a quarterly update ISO as base for mau-extratests1New

Actions
Related to openQA Tests - action #107620: [qe-core] Please add upgrade test from Leap 15.3 to Leap 15.4Resolvedpunkioudi2022-03-08

Actions
Related to openQA Tests - action #107965: [qe-core] add gm qcows to fixed hdd directory for leap in o3Resolvedszarate2022-03-08

Actions
Related to openQA Tests - action #108692: [qe-core] Leap offline migration - do not skip releases (15.0 -> 15.1 -> 15.2 -> 15.3)Resolvedmloviska

Actions
Related to openQA Tests - coordination #108797: [qe-core] Leap setup 15.4 openqa for updatesBlocked2022-05-18

Actions
Actions #1

Updated by okurz almost 3 years ago

  • Related to action #89263: [leap 15.3][qe-core] Please add migration testing from 15.2 to 15.3 and remove migration tests from 42.X added
Actions #2

Updated by tjyrinki_suse almost 3 years ago

  • Category set to Enhancement to existing tests
  • Status changed from New to Workable
  • Start date deleted (2021-04-22)
Actions #3

Updated by tjyrinki_suse almost 3 years ago

  • Subject changed from [qem][qe-core] Consider updating GM images before running migration tests to [qem][qe-core][needs-refining] Consider updating GM images before running migration tests
Actions #4

Updated by szarate over 2 years ago

  • Subject changed from [qem][qe-core][needs-refining] Consider updating GM images before running migration tests to [qem][leap][opensuse][qe-core][needs-refining] Consider updating GM images before running migration tests
Actions #5

Updated by okurz over 2 years ago

  • Related to action #97487: Optimize installation of incident repos in SLE maintenance full tests added
Actions #6

Updated by okurz over 2 years ago

  • Related to action #97484: [qe-core] Use a quarterly update ISO as base for mau-extratests1 added
Actions #7

Updated by apappas about 2 years ago

  • Target version set to QE-Core: Ready
Actions #8

Updated by tjyrinki_suse about 2 years ago

  • Subject changed from [qem][leap][opensuse][qe-core][needs-refining] Consider updating GM images before running migration tests to [qem][leap][opensuse][qe-core] Consider updating GM images before running migration tests
  • Description updated (diff)
Actions #9

Updated by tjyrinki_suse about 2 years ago

  • Subject changed from [qem][leap][opensuse][qe-core] Consider updating GM images before running migration tests to [qem][leap][opensuse][qe-core] Update GM images before running migration tests
Actions #10

Updated by szarate about 2 years ago

  • Related to action #107620: [qe-core] Please add upgrade test from Leap 15.3 to Leap 15.4 added
Actions #11

Updated by tjyrinki_suse about 2 years ago

  • Subject changed from [qem][leap][opensuse][qe-core] Update GM images before running migration tests to [qem][leap][opensuse][qe-core] Update GM images before running upgrade tests
  • Description updated (diff)
Actions #12

Updated by tjyrinki_suse about 2 years ago

  • Description updated (diff)
Actions #13

Updated by tjyrinki_suse about 2 years ago

  • Related to action #107965: [qe-core] add gm qcows to fixed hdd directory for leap in o3 added
Actions #14

Updated by apappas almost 2 years ago

  • Assignee set to apappas
Actions #15

Updated by szarate almost 2 years ago

Anton, see https://progress.opensuse.org/issues/108692 before working on this

Actions #16

Updated by szarate almost 2 years ago

Is the status of this ticket current? any updates? can we resolve the ticket?

Actions #17

Updated by apappas almost 2 years ago

  • Status changed from Workable to In Progress
Actions #18

Updated by apappas almost 2 years ago

At first I wanted to resolve this ticket by updating the migration images and not adding any other module to the migration runs, because qcows of EOLd should be at a steady end state. However as I was investigating this, I found out that the qcow images can become unbootable/corrupted without the migration test realizing that.

It is great that yast can deal with that, but we should be testing a proper system, so I will both upload an updated qcow image and add a patch_and_reboot module as a sanity check.

Actions #19

Updated by mloviska almost 2 years ago

  • Related to action #108692: [qe-core] Leap offline migration - do not skip releases (15.0 -> 15.1 -> 15.2 -> 15.3) added
Actions #20

Updated by mloviska almost 2 years ago

Actions #21

Updated by apappas almost 2 years ago

  • Status changed from In Progress to Feedback

I need a way to get access to o3 development mode to continue with this ticket.

Actions #22

Updated by slo-gin 8 days ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF