Project

General

Profile

Actions

action #95869

open

[qac] test fails in docker_image likely due to `docker system prune -a -f` timing out

Added by okurz almost 3 years ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-07-22
Due date:
% Done:

0%

Estimated time:
Difficulty:

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

Actions #1

Updated by okurz over 2 years ago

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . Please consider picking up this ticket within the next 30 days or just set the ticket to the next lower priority of "Normal" (SLO: updated within 365 days). This update was done as agreed within the SUSE QE Sync call 2021-09-01

Actions #2

Updated by okurz over 2 years ago

  • Priority changed from High to Normal

This ticket was set to "High" priority but was not updated within the SLO period for "High" tickets (30 days) as described on https://progress.opensuse.org/projects/openqatests/wiki/Wiki#SLOs-service-level-objectives . The ticket will be set to the next lower priority of "Normal".

Actions #3

Updated by slo-gin over 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.

Actions #4

Updated by slo-gin about 1 month 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.

Actions

Also available in: Atom PDF