action #113450
open[qac][container][podman][azure] test fails in podman due to zypper error auto_review:"Media source .*http://download.opensuse.org/tumbleweed/repo/oss/.* does not contain the desired medium":retry
0%
Description
Observation¶
openQA test in scenario sle-15-SP3-AZURE-CHOST-BYOS-Updates-x86_64-publiccloud_containers@64bit fails in
podman
due to zypper error "Media source 'http://download.opensuse.org/tumbleweed/repo/oss/' does not contain the desired medium"
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Have not seen other occurences of the very same problem but we know about zypper problems in general, e.g. see https://github.com/openSUSE/zypper/issues/420
Expected result¶
https://openqa.suse.de/tests/9095324 shows a successful match but it was a "lucky match" as the problem can reappear anytime depending on specific timing.
Impact¶
I found this test failure reviewing SLE maintenance test results which were blocking automatic approval meaning that test failures like these block automatic SLE maintenance update releases hence the issue should be treated with urgency.
Suggestions¶
- Add a test suite description, currently it's just the base test template
- Add retry around the zypper call, e.g. using https://software.opensuse.org/package/retry
Further details¶
Always latest result in this scenario: latest
Updated by okurz almost 3 years ago
- Subject changed from [qac][container][podman][azure] test fails in podman due to zypper error auto_review:"Media source 'http://download.opensuse.org/tumbleweed/repo/oss/' does not contain the desired medium":retry to [qac][container][podman][azure] test fails in podman due to zypper error auto_review:"Media source .*http://download.opensuse.org/tumbleweed/repo/oss/.* does not contain the desired medium":retry
Updated by slo-gin about 1 year ago
This ticket was set to Normal 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.
Updated by slo-gin about 2 months ago
- Priority changed from Normal to Low
This ticket was set to Normal priority but was not updated within the SLO period. The ticket will be set to the next lower priority Low.