Project

General

Profile

Actions

action #174451

open

QA (public) - coordination #162890: [saga][epic] feature discoverability

coordination #162896: [epic] Job triggering on jobless openQA instances

openQA-in-openQA tests can get stuck with an inconsistent repository

Added by mkittler 3 days ago. Updated 3 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Regressions/Crashes
Target version:
Start date:
2024-12-16
Due date:
% Done:

0%

Estimated time:

Description

Observation

After #167395 openQA-in-openQA tests use devel:openQA:testing which is a snapshot of devel:openQA created before triggering tests. Unfortunately this snapshot can be created at a bad time where the repository is inconsistent. At least that's how it looks like on https://openqa.opensuse.org/tests/4704845#step/openqa_worker/1 where the installation of openQA-worker fails with The to be installed openQA-worker-4.6.17… requires 'openqa-common = 4.6.17… … but this requirement cannot be provided. Then it suggests do downgrade to packages from openSUSE.

The tests retries the installation but because devel:openQA:testing is snapshotted after #167395 this is in vain now.

I checked the video and it looks like the test really only adds devel:openQA:testing (and not e.g. devel:openQA in addition). So I think an inconsistent snapshot of devel:openQA:testing is the most likely explanation.

Acceptance criteria

  • AC1: Tests are only triggered from a consistent snapshot of devel:openQA

Related issues 1 (0 open1 closed)

Related to openQA Project (public) - action #167395: Ensure only the tested revision of devel:openQA packages are submitted to openSUSE:Factory size:MResolvedmkittler2024-09-252024-12-12

Actions
Actions

Also available in: Atom PDF