[epic] test incompletes after failing in GRU download task on "Inactivity timeout" with no logs
openQA test in scenario obs-Unstable-Appliance-x86_64-obs_appliance@64bit-4G incompletes after failing in
Gru job failed Reason: asset download: download of http://download.opensuse.org/repositories/OBS:/Server:/Unstable/images/obs-server.x86_64-2.10.51-qcow2-Build2.438.qcow2 to /var/lib/openqa/share/factory/hdd/obs-server.x86_64-2.10.51-qcow2-Build2.438.qcow2 failed: connection error: Inactivity timeout at /usr/share/openqa/script/../lib/OpenQA/Task/Asset/Download.pm line 74.
ending the complete job in "incomplete".
Hard, seems to be related to temporary network problems.
- AC1: GRU download retries automatically on temporary network problems
- AC2: The way we provide feedback to users is comparable for GRU download failures as well as other incompletes with known reasons
I realized the quite different approach for user feedback on GRU download jobs vs. other incompletes with mkittler already on 2020-01-21. Retry is just one part of it. Maybe the way how GRU download jobs provide details but still incomplete is the way to go?
Always latest result in this scenario: latest
#1 Updated by kraih over 1 year ago
Might be interesting to combine the cache service and gru download code into a shared module, and get retry support that way. Both do pretty much the same thing. It's a bit of upfront work, but later on we'd benefit from being able to test the various special cases for downloads in one place. And bugfixes would automatically apply to both.
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html