action #132572
closed[qe-c] test fails in podman_netavark
0%
Description
Observation¶
openQA test in scenario opensuse-15.5-DVD-Updates-x86_64-extra_tests_textmode_podman_containers@64bit fails in
podman_netavark
Test suite description¶
Maintainer: dheidler. Extra tests about CLI software in container module
Reproducible¶
Fails since (at least) Build 20230711-2
Expected result¶
Last good: 20230711-1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by rfan1 over 1 year ago
Seems we missed the bci img:
Trying to pull registry.opensuse.org/bci/bci-busybox:latest...
Error: choosing an image from manifest list docker://registry.opensuse.org/bci/bci-busybox:latest: no image found in manifest list for architecture amd64, variant "", OS linux
FSeMq-125-
Updated by rfan1 over 1 year ago
The issue is addressed in:
https://suse.slack.com/archives/C02CGKBCGT1/p1689143703909509
Updated by rfan1 over 1 year ago
- Status changed from New to In Progress
- Assignee set to rfan1
Updated by dancermak over 1 year ago
The correct url is registry.opensuse.org/opensuse/bci/bci-busybox:latest
Updated by rfan1 over 1 year ago
dancermak wrote:
The correct url is
registry.opensuse.org/opensuse/bci/bci-busybox:latest
Thanks much @dancermak, let me do that!
Updated by jlausuch over 1 year ago
- Tags changed from bugbusters to bugbusters, bug
- Project changed from openQA Tests (public) to Containers and images
- Subject changed from [qe-core][qe-c]test fails in podman_netavark to [qe-c]test fails in podman_netavark
- Category deleted (
Bugs in existing tests)
Updated by jlausuch over 1 year ago
The reason is that registry.opensuse.org/bci/bci-busybox:latest
is not longer available for x86_64.
Follow-up: https://suse.slack.com/archives/C02CGKBCGT1/p1689143703909509
Updated by jlausuch over 1 year ago
- Subject changed from [qe-c]test fails in podman_netavark to [qe-c] test fails in podman_netavark
- Assignee deleted (
rfan1) - Target version deleted (
QE-Core: Ready)
Updated by jlausuch over 1 year ago
- Status changed from In Progress to Resolved
Resolved. This was already fixed.
Updated by rfan1 over 1 year ago
ph03nix wrote:
Is Richard still working on this?
No, I can see the issue is fixed now, and openqa job is green as well :)