action #95869
open[qac] test fails in docker_image likely due to `docker system prune -a -f` timing out
0%
Description
Observation¶
openQA test in scenario sle-15-Server-DVD-Updates-s390x-sle_image_on_sle_host_docker@s390x-kvm-sle12 fails in
docker_image
when calling the command docker system prune -a -f
. As it looks like the system is just very busy doing that, maybe because pruning all the cached stuff and images within the SUT can actually cause high I/O. Then also even the post_fail_hook fails to login, likely due to the same problem, because the system is very busy: https://openqa.suse.de/tests/6515850#step/docker_image/1836
Test suite description¶
The base test suite is used for job templates defined in YAML documents. It has no settings of its own.
Reproducible¶
Fails since (at least) Build 20210722-1 (current job)
Expected result¶
Last good: 20210721-1 (or more recent)
- Tests should not fail just because
docker system prune -a -f
times out - Test suite description should provide a maintainer and a useful description (not just the standard template description)
Suggestions¶
- Extend timeout for both the
docker system prune
command as well as for the login into the post_fail_hook - Provide a useful description for the test suite
Further details¶
Always latest result in this scenario: latest