action #69448
opencoordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA
coordination #102909: [epic] Prevent more incompletes already within os-autoinst or openQA
test incompletes with auto_review:"(?s)was downloaded by.*details.*unavailable here.*Failed to download":retry , not helpful details
0%
Description
Observation¶
https://openqa.suse.de/tests/4504435 is incomplete with reason "setup failure: Failed to download SLEHPC-15-SP2-x86_64-GM-gnome.qcow2 to /var/lib/openqa/cache/openqa.suse.de/SLEHPC-15-SP2-x86_64-GM-gnome.qcow2" so no explanation of the real reason in there. The log content of autoinst-log.txt as shown on the details page shows:
[2020-07-30T06:03:09.0587 CEST] [debug] [pid:36179] Found HDD_1, caching SLEHPC-15-SP2-x86_64-GM-gnome.qcow2
[2020-07-30T06:03:09.0590 CEST] [info] [pid:36179] Downloading SLEHPC-15-SP2-x86_64-GM-gnome.qcow2, request #22885 sent to Cache Service
[2020-07-30T06:03:14.0667 CEST] [info] [pid:36179] Download of SLEHPC-15-SP2-x86_64-GM-gnome.qcow2 processed:
Asset "SLEHPC-15-SP2-x86_64-GM-gnome.qcow2" was downloaded by #22884, details are therefore unavailable here
[2020-07-30T06:03:14.0671 CEST] [error] [pid:36179] Failed to download SLEHPC-15-SP2-x86_64-GM-gnome.qcow2 to /var/lib/openqa/cache/openqa.suse.de/SLEHPC-15-SP2-x86_64-GM-gnome.qcow2
[2020-07-30T06:03:14.0695 CEST] [info] [pid:36179] +++ worker notes +++
[2020-07-30T06:03:14.0695 CEST] [info] [pid:36179] End time: 2020-07-30 04:03:14
[2020-07-30T06:03:14.0695 CEST] [info] [pid:36179] Result: setup failure
so also not really helpful as the user does not know what "downloaded by #22884" means or how to access these details. Also https://openqa.suse.de/tests/4504435/file/worker-log.txt does not add more.
Acceptance criteria¶
- AC1: The real reason for the download error is accessible in the job details (either "reason" or autoinst-log.txt)
Suggestions¶
- Research what the actual error could be and add it as a "likely explanation" in the existing error string
- Try to include the actual error details into the affected jobs logs
- If possible, adapt the "reason" to be more specific with details about the actual error