Actions
action #110803
closed[tools] openqa_from_containers: test fails in setup_env size:S
Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
Start date:
2022-05-09
Due date:
% Done:
0%
Estimated time:
Difficulty:
Tags:
Description
Observation¶
openQA test in scenario openqa-Tumbleweed-dev-x86_64-openqa_from_containers@64bit-2G fails in
setup_env
The error message from docker suggests, there could be a problem with the docker registry itself (maybe a limit has been exceeded?).
[ 870.989997] dockerd[2355]: time="2022-05-09T07:39:08.406609692-04:00" level=error msg="Handler for POST /v1.41/images/create returned error: Head \"https://registry-1.docker.io/v2/library/postgres/manifests/latest\": Get \"https://auth.docker.io/token?scope=repository%3Alibrary%2Fpostgres%3Apull&service=registry.docker.io\": net/http: request canceled (Client.Timeout exceeded while awaiting headers)"
Retry did help in this case. The actual container image we try to retrieve from the docker hub is "postgres" here.
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.11254 (current job)
Expected result¶
Last good: :TW.11253 (or more recent)
Suggestions¶
- Use podman instead of docker (might actually be relevant to fixing in case of timeouts)
- Consider using a postgres container from the openSUSE registry
- Consider adding retrying around the docker call within the test (we have RETRY on the test)
Further details¶
Always latest result in this scenario: latest
Actions