Project

General

Profile

action #123106

[tools][openQA-in-openQA][sporadic] test fails in docker build size:M

Added by jbaier_cz 5 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Urgent
Assignee:
jbaier_cz
Category:
Bugs in existing tests
Target version:
openQA Project - Ready
Start date:
2023-01-13
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_from_containers@64bit-2G fails in
build

The docker build fails during zypper installation, package openQA-common not found on medium (can be seen on video on mark 4:00). Likely issues with the repository (or its mirror).

Test suite description

Maintainer: okurz@suse.de Test for running openQA itself from containers. To be used with "openqa" distri. Introduced retry on the job level due to https://progress.opensuse.org/issues/108665 as there can still be sporadic network issues sometimes.

Reproducible

Fails since (at least) Build :TW.15047

Expected result

Last good: :TW.15046 (or more recent)

Further details

Always latest result in this scenario: latest

Related issues

Related to openQA Project - action #119245: openQA in openQA test fails in docker buildResolved2022-10-24

Related to openQA Tests - action #123496: [tools][openQA-in-openQA][sporadic] test fails in worker because of GNOME authentication dialog size:MResolved2023-01-232023-03-17

History

#1 Updated by jbaier_cz 5 months ago

  • Related to action #119245: openQA in openQA test fails in docker build added

#2 Updated by jbaier_cz 5 months ago

  • Target version set to Ready

#3 Updated by okurz 5 months ago

  • Priority changed from Normal to Urgent

#4 Updated by jbaier_cz 5 months ago

  • Assignee set to jbaier_cz

#5 Updated by mkittler 5 months ago

  • Subject changed from [tools][openQA-in-openQA][sporadic] test fails in docker build to [tools][openQA-in-openQA][sporadic] test fails in docker build size:M
  • Status changed from New to Workable

#6 Updated by jbaier_cz 5 months ago

  • Status changed from Workable to In Progress

The failure we see is still during the docker build, i.e. within the Dockerfile. It seems to me, that it is not desirable nor correct to complicate the Dockerfile with the retry logic. So I will try solve that on the test level. Maybe I would be able to parse the docker output and rerun for zypper issues or at least record_info with this progress ticket for some automatic processing.

#7 Updated by openqa_review 5 months ago

  • Due date set to 2023-02-03

Setting due date based on mean cycle time of SUSE QE Tools

#8 Updated by jbaier_cz 5 months ago

Known error during zypper operation is recognized and recorded: https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/106

Maybe we can then use auto-review to handle and label the failure?

#9 Updated by cdywan 4 months ago

jbaier_cz wrote:

Known error during zypper operation is recognized and recorded: https://github.com/os-autoinst/os-autoinst-distri-openQA/pull/106

We brainstormed some ideas for a follow-up in case both extending the timeout and the number of attempts aren't good enough. 1) OBS never builds with internet connectivity, and the only reliable option would be to avoid that here as well. 2) Ultimately the test fails on a missing external dependency, maybe we could handle that after the job fails if we can reliably detect it.

For now we probably want to increase the number of attemps since we already get exponential back-off's (commente don the PR).

#11 Updated by jbaier_cz 4 months ago

  • Due date deleted (2023-02-03)
  • Status changed from In Progress to Resolved

The code with more attempts is online, we will see if that helped eventually.

#12 Updated by jbaier_cz 4 months ago

  • Related to action #123496: [tools][openQA-in-openQA][sporadic] test fails in worker because of GNOME authentication dialog size:M added

Also available in: Atom PDF