action #76813
Updated by livdywan almost 3 years ago
## Observation * See title and https://openqa.suse.de/tests/4913987 * At the time of creating the ticket the job has been restarted manually and the clone passed. ``` [2022-01-13T13:57:24.238682+01:00] [warn] !!! consoles::VNC::login: Error connecting to VNC server <10.161.145.92:5901>: IO::Socket::INET: connect: Connection refused ``` ## Steps to reproduce Find jobs referencing this ticket with the help of https://raw.githubusercontent.com/os-autoinst/scripts/master/openqa-query-for-job-label , call `openqa-query-for-job-label poo#76813` ## Acceptance criteria * **AC1:** It is clear to test reviewers what needs to be done in the next step when reading the reason ## Suggestions This looks like a temporary problem with the svirt host (here `openqaw5-xen.qa.suse.de`). But it is not clear whether the problem is always temporary and an automatic restart would make sense. I mainly created this ticket so jobs like this one won't show up in auto-review anymore. - What workers are affected? Is it openqaworker2 and grenache only? Yes, obviously because only them use the svirt backend ## Steps to reproduce Find jobs referencing this way. - Focus on tests trying to connect to a remote machine - Add better log messages explaining to test reviewers what the message could mean - Make sure the test ends ticket with a proper reason propagated into the job results ## Out help of scope - VNC running on localhost https://raw.githubusercontent.com/os-autoinst/scripts/master/openqa-query-for-job-label , call `openqa-query-for-job-label poo#76813`