Project

General

Profile

Actions

action #51857

open

coordination #39302: [qe-core][functional][opensuse][epic][medium] uefi upgrade tests on TW+Leap (was: missing assets)

[qe-core][functional] create scenario upgrade_tumbleweed which uses released ISO instead of tested ISO and publishes the qcow2 for extra tests

Added by ggardet_arm almost 5 years ago. Updated about 1 month ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
New test
Target version:
SUSE QA - Milestone 30
Start date:
2019-05-22
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Observation

As a release manager, I want to have a real use case scenario where a user has a released tumbleweed snapshot installed which is then upgraded to the to be released snapshot.

upgrade_tumbleweed should use released ISO instead of tested ISO, otherwise, installer may fail to boot properly.

openQA test in scenario opensuse-Tumbleweed-NET-aarch64-create_hdd_tumbleweed@aarch64 fails in
welcome

Acceptance criteria

  • AC: The use case of upgrading a released snapshot to the snapshot to be tested is covered in openQA

Tasks

  1. Proper scenario's name to be decided.
  2. Monitor the snapshot releases, when a new snapshot is released save the corresponding qcow2 image in the fixed directory
  3. Once there's a new snapshot released, remove the previous 'published'
  4. Update the repositories

Reproducible

Fails since Build 20190304

Expected result

Last good: 20190304

Further details

Always latest result in this scenario: latest

Actions #1

Updated by SLindoMansilla almost 5 years ago

  • Subject changed from create_hdd_tumbleweed should use released ISO instead of tested ISO to [functional][u] create_hdd_tumbleweed should use released ISO instead of tested ISO
  • Description updated (diff)
  • Priority changed from Normal to High

As a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).

Please, feel free to adjust the category or the "[label]" if you think different.

Actions #2

Updated by szarate almost 5 years ago

DimStar: well, I know fo the 'special case' create_hdd-tumbleweed in TW: we use that to install 'the latest, published TW snapshot - which the user is likely to have installed if they follow a regular update method' - and from that image, we run a zypper dup (tw2twnext test) to verify if we can upgrade from the published snapshot to the one under test.

The idea of the test suite is to create an installation from the last published snapshot so that we can do the upgrade from last_published to current snapshot_under_test as a test

Actions #4

Updated by SLindoMansilla almost 5 years ago

  • Subject changed from [functional][u] create_hdd_tumbleweed should use released ISO instead of tested ISO to [functional][u] create scenario upgrade_tumbleweed which uses released ISO instead of tested ISO and publishes the qcow2 for extra tests
  • Description updated (diff)
  • Status changed from New to Workable
  • Priority changed from High to Normal
  • Target version set to Milestone 26
Actions #5

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 26 to Milestone 27
Actions #6

Updated by SLindoMansilla over 4 years ago

  • Parent task set to #39302
Actions #7

Updated by SLindoMansilla over 4 years ago

  • Estimated time set to 42.00 h
Actions #8

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 27 to Milestone 28
Actions #9

Updated by szarate over 4 years ago

So not only I had to run with a similar situation (But on SLES), but Defolos is also needeing something similar to this, as it could help him with https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/8883. Maybe let's pick it up next week.

Actions #10

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 28 to Milestone 30

needs to be discussed offline

Actions #11

Updated by ggardet_arm over 4 years ago

Still a problem (probably due to the kernel update): https://openqa.opensuse.org/tests/1146526

Actions #12

Updated by mgriessmeier over 4 years ago

  • Priority changed from Normal to High

let'S do this, seems to be fairly easy

Actions #13

Updated by okurz about 4 years ago

  • Priority changed from High to Low

As discussed with mgriessmeier: That's actually a valid request for additional test coverage but not "Bugs". And as can be seen in the ticket id this is already a bit older, hence not really "High", right?

Actions #14

Updated by okurz about 4 years ago

  • Category changed from Bugs in existing tests to New test
Actions #15

Updated by SLindoMansilla almost 4 years ago

  • Priority changed from Low to Normal
Actions #16

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from [functional][u] create scenario upgrade_tumbleweed which uses released ISO instead of tested ISO and publishes the qcow2 for extra tests to [qe-core][functional] create scenario upgrade_tumbleweed which uses released ISO instead of tested ISO and publishes the qcow2 for extra tests
Actions #17

Updated by okurz over 2 years ago

I came to this ticket due to periodically reviewing tickets as described on https://progress.opensuse.org/projects/openqatests/wiki#How-we-work-on-tickets

This ticket was set to "Normal" priority but was not updated within the SLO period for "Normal" tickets (365 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives

First reminder: Please consider picking up this ticket within the next 365 days or just set the ticket to the next lower priority of "Low" (no SLO related time period).

Actions #18

Updated by slo-gin over 1 year 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 #19

Updated by slo-gin about 1 month 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