action #42452
openopenQA-in-openQA test fails in openqa_webui trying to access a TW snapshot repo on o3 that is already deleted and the test does not track the repo
0%
Description
Observation¶
openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_install+publish@64bit-2G fails in
openqa_webui
Reproducible¶
Fails since (at least) Build :TW.1772
Expected result¶
Last good: :TW.1771 (or more recent)
Suggestions¶
the repo of TW snapshot 20181011 is already deleted when trying to install packages from it. Maybe it is just as simple as specifying the repo in e.g. REPO_1=… so that openQA would track the job as dependant on the snapshot and not delete it that fast.
Further details¶
Always latest result in this scenario: latest
Updated by SLindoMansilla almost 6 years ago
- Status changed from Workable to In Progress
- Assignee set to SLindoMansilla
Updated by SLindoMansilla almost 6 years ago
Setting added to test suite openqa_install+publish:
Updated by okurz almost 6 years ago
I doubt this can work. Builds for the openQA-in-openQA tests are named like ":TW.1884" and not like 20181217
Updated by SLindoMansilla almost 6 years ago
- Status changed from In Progress to Workable
- Assignee deleted (
SLindoMansilla)
Updated by okurz almost 6 years ago
There is a jenkins job triggering the tests, see http://jenkins.qa.suse.de/view/openQA-in-openQA/
https://gitlab.suse.de/openqa/scripts/blob/master/trigger-openqa_in_openqa is the trigger script where we could mention REPO_0 referencing the TW repo.
Updated by okurz almost 6 years ago
- Target version changed from Milestone 21 to Milestone 25+
Updated by mgriessmeier over 5 years ago
- Target version changed from Milestone 25+ to Milestone 25
Updated by mgriessmeier over 5 years ago
- Status changed from Workable to Rejected
- Assignee set to mgriessmeier
Updated by okurz over 5 years ago
- Status changed from Rejected to Workable
can you explain why you reject this? I guess the issue is still valid, is it not?
Updated by okurz over 5 years ago
- Assignee deleted (
mgriessmeier) - Target version changed from Milestone 25 to future
discussed with @mgriessmeier in person: Issue still valid, could reappear at any time when someone e.g. triggers a slightly older test job and in case the corresponding Tumbleweed repo was already deleted. The main reason we use a snapshot qcow image is to have a convenient image including gnome which AFAIK we don't have available from JeOS or anything. So I can think of three alternatives:
- Make sure the proper TW repos are tracked on o3
- Replace the repos with published ones
- use a different image that already has only published repos
Updated by SLindoMansilla about 5 years ago
- Subject changed from [openqa][functional][u] openQA-in-openQA test fails in openqa_webui trying to access a TW snapshot repo on o3 that is already deleted and the test does not track the repo to [openqa][opensuse] openQA-in-openQA test fails in openqa_webui trying to access a TW snapshot repo on o3 that is already deleted and the test does not track the repo
- Assignee set to okurz
We, u-team, prefer to not handle this extra product
Updated by okurz about 5 years ago
- Blocked by action #12180: [webui] Prevent tests to be triggered when required assets are not present (anymore) added
Updated by okurz about 5 years ago
- Project changed from openQA Tests to openQA Project
- Subject changed from [openqa][opensuse] openQA-in-openQA test fails in openqa_webui trying to access a TW snapshot repo on o3 that is already deleted and the test does not track the repo to openQA-in-openQA test fails in openqa_webui trying to access a TW snapshot repo on o3 that is already deleted and the test does not track the repo
- Category changed from Bugs in existing tests to Feature requests
- Status changed from Workable to Blocked
- Target version deleted (
future)
Updated by okurz almost 5 years ago
latest failure: https://openqa.opensuse.org/tests/1118088#step/openqa_webui/7
Updated by okurz about 4 years ago
- Status changed from Blocked to Workable
- Assignee deleted (
okurz) - Priority changed from Normal to Low
- Target version changed from Ready to future