action #99402
closed
Incompletes with "backend died: Error connecting to VNC server.*: IO::Socket::INET: connect: Connection timed out":retry should be restarted automatically
Added by okurz about 3 years ago.
Updated about 3 years ago.
Category:
Regressions/Crashes
Description
motivation¶
Similar to #99396
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#99402
acceptance criteria¶
- AC1: Incomplete jobs with a reason matching the regex from the ticket title (or possibly a less strict version) should be restarted automatically.
suggestions¶
- Try to configure this via settings in
openqa.ini.
- Otherwise consider extending the code.
- Copied from action #99396: Incompletes with auto_review:"api failure: Failed to register .* 503":retry should be restarted automatically added
- Status changed from In Progress to Feedback
- Subject changed from Incompletes with auto_review:"backend died: Error connecting to VNC server.*: IO::Socket::INET: connect: Connection timed out":retry should be restarted automatically to Incompletes with "backend died: Error connecting to VNC server.*: IO::Socket::INET: connect: Connection timed out":retry should be restarted automatically
- Description updated (diff)
- Due date changed from 2021-10-12 to 2021-10-22
The PR was merged 13 days ago and is effective on OSD as we do not overwrite the default in /etc/openqa/openqa.ini
The command openqa-query-for-job-label poo#99402 yields:
7370318|2021-10-11 05:42:34|done|incomplete|create_hdd_minimal_base+sdk_withhome|backend died: Error connecting to VNC server <10.161.145.91:5901>: IO::Socket::INET: connect: Connection timed out|grenache-1
7328412|2021-10-06 16:33:14|done|incomplete|create_hdd_autoyast_containers|backend died: Error connecting to VNC server <10.161.145.97:5901>: IO::Socket::INET: connect: Connection timed out|grenache-1
7264783|2021-09-29 18:02:52|done|incomplete|qam-sles4sap_online_dvd_gnome_hana_nvdimm|backend died: Error connecting to VNC server <holmes.qa.suse.de:5901>: IO::Socket::INET: connect: Connection timed out|grenache-1
7239186|2021-09-27 02:27:56|done|incomplete|create_hdd_gnome|backend died: Error connecting to VNC server <10.161.145.90:5901>: IO::Socket::INET: connect: Connection timed out|grenache-1
7235550|2021-09-26 13:32:40|done|incomplete|qam-minimal+base|backend died: Error connecting to VNC server <10.161.145.93:5901>: IO::Socket::INET: connect: Connection timed out|grenache-1
7235313|2021-09-26 13:26:57|done|incomplete|mru-install-minimal-with-addons|backend died: Error connecting to VNC server <10.161.145.97:5901>: IO::Socket::INET: connect: Connection timed out|grenache-1
7233843|2021-09-26 02:15:44|done|incomplete|mru-install-minimal-with-addons|backend died: Error connecting to VNC server <10.161.145.93:5901>: IO::Socket::INET: connect: Connection timed out|grenache-1
7233818|2021-09-26 02:12:45|done|incomplete|qam-minimal+base|backend died: Error connecting to VNC server <10.161.145.95:5901>: IO::Socket::INET: connect: Connection timed out|grenache-1
7233131|2021-09-26 01:28:13|done|incomplete|qam-gnome|backend died: Error connecting to VNC server <10.161.145.95:5901>: IO::Socket::INET: connect: Connection timed out|grenache-1
7232532|2021-09-26 01:26:25|done|incomplete|mru-install-minimal-with-addons|backend died: Error connecting to VNC server <10.161.145.90:5901>: IO::Socket::INET: connect: Connection timed out|grenache-1
I checked the first two jobs 7370318 and 7328412 . Both have been cloned but I could not find a reference in the audit log https://openqa.suse.de/admin/auditlog for these jobs. Maybe this really means that openQA cloned these jobs automatically and we did not even need to rely on auto-review which would likely show up as "geekotest" in the auditlog. I will remove the "auto_review" prefix in the ticket subject and monitor over the next time.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF