Project

General

Profile

Actions

action #164222

open

Client error messages look like http response codes - we should phrase them better - was: asset download fails with "521 Connect timeout"

Added by okurz 8 days ago. Updated 5 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Regressions/Crashes
Target version:
Start date:
2024-07-19
Due date:
2024-08-03 (Due in 7 days)
% Done:

0%

Estimated time:

Description

Observation

https://openqa.suse.de/tests/14969481#step/GRU/1 shows

preparation failed: Downloading "http://automotive-3.arch.suse.de/gitlab/chuller/carwos-chuller_carwos1.1-2850918.qcow2" failed with: Download of "/var/lib/openqa/share/factory/hdd/carwos-chuller_carwos1.1-2850918.qcow2" failed: 521 Connect timeout 

and a lot of others in the same job group. Apparently this happened because chuller wants to "resurrect" the carwos tests and struggles to get the communication up and running again. This can happen but we should ensure that we can read error messages correctly. Here the "521 Connect timeout" looks like an http response from "the server" but really seems to be a response from the client. Maybe mojo requests produce errors looking similar to http response codes. We should ensure these are properly labeled so that people cannot confuse them with responses from the server.

Suggestions

  • Find the code responsible for downloading this (is it test code? Minion code? Something else?) and improve its log message

Rollback steps

Actions

Also available in: Atom PDF