Project

General

Profile

Actions

action #55877

open

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

[qe-core][functional] Describe the process on how we get a Leap scenario to a Tumbleweed

Added by SLindoMansilla over 4 years ago. Updated 13 days ago.

Status:
Feedback
Priority:
Normal
Assignee:
-
Category:
Spike/Research
Target version:
SUSE QA - Milestone 31
Start date:
2019-08-24
Due date:
% Done:

0%

Estimated time:
42.00 h
Difficulty:

Description

Use story

As a new QA member who doesn't know enough about openQA, I want to know how to get a upgrade scenario that upgrades from Leap 42.3 or Leap 15.0 or Leap 15.1 (etc) to Tumbleweed.

AC

  1. Process is described and documented under https://confluence.suse.com/display/qasle/How+to%27s+and+workflows (Where the assets are, and what steps are to be carried), and abstract enough to be understandable without the need of in depth knowledge of the openQA setups

Related issues 2 (0 open2 closed)

Blocked by openQA Tests - action #12964: [qe-core][functional][migration] Boot to snapshot after upgrade and then rollbackResolvedzluo

Actions
Follows openQA Tests - action #55874: [qe-core][functional] Create matrix about possible upgrade scenarios in combination with machine types distribution versionRejected2019-08-23

Actions
Actions #1

Updated by SLindoMansilla over 4 years ago

  • Follows action #55874: [qe-core][functional] Create matrix about possible upgrade scenarios in combination with machine types distribution version added
Actions #2

Updated by mgriessmeier over 4 years ago

  • Target version set to Milestone 28
Actions #3

Updated by SLindoMansilla over 4 years ago

  • Status changed from New to Workable
  • Priority changed from High to Low
  • Estimated time set to 42.00 h
Actions #4

Updated by mgriessmeier over 4 years ago

  • Target version changed from Milestone 28 to Milestone 31
Actions #5

Updated by SLindoMansilla about 4 years ago

  • Subject changed from [functional][u] Describe the process on we get a Leap scenario to a Tumbleweed to [functional][u] Describe the process on how we get a Leap scenario to a Tumbleweed
  • Priority changed from Low to Normal
Actions #6

Updated by dheidler almost 4 years ago

Don't we already have that?
eg: https://openqa.opensuse.org/tests/1273336

Actions #7

Updated by zluo over 3 years ago

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

well, zdup hat been removed now.

I'm working at moment on https://progress.opensuse.org/issues/12964 which use upgrade workflow for boot_into_snapshot_after_upgrade.

Will provide further information when my PR got merged.

Actions #8

Updated by szarate over 3 years ago

  • Blocked by action #12964: [qe-core][functional][migration] Boot to snapshot after upgrade and then rollback added
Actions #9

Updated by szarate over 3 years ago

  • Status changed from In Progress to Blocked
Actions #10

Updated by tjyrinki_suse over 3 years ago

  • Subject changed from [functional][u] Describe the process on how we get a Leap scenario to a Tumbleweed to [qe-core][functional] Describe the process on how we get a Leap scenario to a Tumbleweed
Actions #11

Updated by zluo over 3 years ago

  • Status changed from Blocked to Resolved

opensuse-Tumbleweed-DVD-x86_64-Build20201124-upgrade_Leap_15.1_gnome@64bit
https://openqa.opensuse.org/tests/1483741

this test suite can be used to describe the process on how we get Leap 15.1 to Tumbleweed.
boot from Tumbleweed DVD: upgrade Leap to Tumbleweed, boot into snapshot

If we have problem with upgrade, then we can rollback to Leap:
opensuse-Tumbleweed-DVD-x86_64-Build20201124-upgrade_boot-into_snapshot_rollback_Leap_15.1_gnome@64bit
https://openqa.opensuse.org/tests/1483552

Actions #12

Updated by szarate over 3 years ago

  • Description updated (diff)
  • Status changed from Resolved to Workable
  • Assignee deleted (zluo)
Actions #13

Updated by okurz over 2 years ago

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. 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 #14

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 #15

Updated by slo-gin 2 months 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 #16

Updated by mgrifalconi 13 days ago

  • Status changed from Workable to Feedback

@szarate is this a low hanging fruit? Just needing documentation to be published about something already done? Or can we just close it? I would be against keeping it forever waiting

Actions

Also available in: Atom PDF