Project

General

Profile

Actions

action #25124

closed

[tools][sprint 201709.1] Workers disconnects from websocket server and getting stuck: job shows as 'State: assigned' forever

Added by AdamWill over 6 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Regressions/Crashes
Target version:
-
Start date:
2017-09-08
Due date:
% Done:

0%

Estimated time:

Description

So with a git checkout from 20170907, we're still seeing workers get stuck in the Fedora openQA instances. The symptoms are:

after that it just does that same thing over and over - 'Sending worker status', with the occasional 'uninitialized value' error - until I restart the process.

I see that there's one further tweak to the scheduler code this morning:
https://github.com/os-autoinst/openQA/pull/1450

I'll deploy that, and see if it helps.


Related issues 2 (0 open2 closed)

Related to openQA Project - coordination #32851: [tools][EPIC] Scheduling redesignResolvedokurz2018-05-05

Actions
Related to openQA Project - action #35296: Error messages on worker about "Use of uninitialized value $host in hash element at /usr/share/openqa/script/../lib/OpenQA/Worker/Common.pm line 359, <GEN298662> line 4."Rejected2018-04-20

Actions
Actions

Also available in: Atom PDF