Project

General

Profile

Actions

action #166907

open

Limit external resources on container tests in Staging

Added by ph03nix 4 months ago. Updated about 2 months ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2024-09-17
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Motivated by a failure in the openQA test in scenario sle-micro-6.0-Default-qcow-Updates-Staging-aarch64-slem_podman@aarch64 - We need to reconsider the currently used external resources (containers) in the Staging test runs.

Staging test runs must be as stable as possible, relying on as little external resources as possible. They are only a very narrow test, the heavy lifting happens in Product Increments.

As such it looks like we're doing too much in Staging. We need to reconsider which images are being used and reduce it to a minimum.

Acceptance criteria

  • The number of container images for Staging test runs is reduced to a minimum so that we can do some very basic tests but not more.
  • The coverage of Product Increment test runs is not affected.
Actions #1

Updated by slo-gin 3 months ago

This ticket was set to High 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 #2

Updated by szarate 3 months ago ยท Edited

This should not only be limited to SLE micro, but also for openSUSE Microos and Tumbleweed - also #168448 is loosely related

Actions #3

Updated by ph03nix 3 months ago

szarate wrote in #note-2:

This should not only be limited to SLE micro, but also for openSUSE Microos and Tumbleweed - also #168448 is loosely related

Factory first always applies, of course!

Actions #4

Updated by slo-gin about 2 months ago

  • Priority changed from High to Normal

This ticket was set to High priority but was not updated within the SLO period. The ticket will be set to the next lower priority Normal.

Actions

Also available in: Atom PDF