Project

General

Profile

Actions

action #112154

closed

test fails in registry

Added by jlausuch about 2 years ago. Updated about 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Target version:
-
Start date:
2022-06-08
Due date:
% Done:

100%

Estimated time:
Tags:

Description

Observation

openQA test in scenario sle-15-SP3-Server-DVD-Updates-x86_64-docker_tests@64bit fails in
registry

Also Tumbleweed: https://openqa.opensuse.org/tests/2405083#step/registry/191

Due to https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15022
There were no VRs for docker tests. Apparently runc test is affected by this change.

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

Reproducible

Fails since (at least) Build 20220607-1

Expected result

Last good: 20220606-1 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by ph03nix about 2 years ago

I need to check if https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15022 introduced a test regression. For testing that I'm gonna use https://openqa.opensuse.org/tests/2405083 and clone a job with the reverted PR under question: https://duck-norris.qam.suse.de/t8923

Actions #2

Updated by jlausuch about 2 years ago

  • Description updated (diff)
Actions #3

Updated by jlausuch about 2 years ago

ph03nix wrote:

I need to check if https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/15022 introduced a test regression. For testing that I'm gonna use https://openqa.opensuse.org/tests/2405083 and clone a job with the reverted PR under question: https://duck-norris.qam.suse.de/t8923

yes, it does, TW is also affected. The problem is that there were no VRs using docker jobs, and registry test module also uses podman to run some commands...

Actions #4

Updated by ph03nix about 2 years ago

  • Status changed from Workable to In Progress
  • Assignee set to ph03nix
Actions #6

Updated by ph03nix about 2 years ago

I have an idea what could have caused this regression. Will try to provide a fix in the next 20 minutes otherwise we can revert the PR.

Actions #9

Updated by jlausuch about 2 years ago

Good catch!

Actions #10

Updated by ph03nix about 2 years ago

Fix pushed, will restart the failed job runs now.

Actions #11

Updated by ph03nix about 2 years ago

  • % Done changed from 0 to 100

Looks like the issue is gone.

Actions #12

Updated by ph03nix about 2 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF