Project

General

Profile

Actions

action #44351

closed

[ipmi] Workers/jobs stuck

Added by xlai over 5 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
-
Start date:
2018-11-26
Due date:
% Done:

0%

Estimated time:

Description

Currently at least 4 ipmi workers (openqaworker2:23/24/25/26) are stuck. They can not finish jobs or take new jobs for over a day and some even several days.

Despite the misleading message from the developer mode, this issue has nothing to do with the developer mode. (The misleading message is also already fixed on latest master.)

This issue is likely tied to the latest refactoring of the worker cache. At least the autoinst-log.txt leads to that conclusion:

tail -f /var/lib/openqa/pool/26/autoinst-log.txt 
[2018-11-26T11:07:10.0806 CET] [info] +++ setup notes +++
[2018-11-26T11:07:10.0806 CET] [info] start time: 2018-11-26 10:07:10
[2018-11-26T11:07:10.0806 CET] [info] running on openqaworker2:26 (Linux 4.7.5-2.g02c4d35-default #1 SMP PREEMPT Mon Sep 26 08:11:45 UTC 2016 (02c4d35) x86_64)
[2018-11-26T11:07:10.0829 CET] [debug] Downloading SLE-15-SP1-Installer-DVD-x86_64-Build100.4-Media1.iso - request sent to Cache Service.

Since spvm jobs on grenache show the same symptom, this is likely also not ipmi-specific.

Job links: https://openqa.suse.de/tests/2272494 (openqaworker2), https://openqa.suse.de/tests/2278365 (grenache-1)


Related issues 1 (0 open1 closed)

Related to openQA Project - action #44363: Exit worker with non-zero return code in error casesResolvedmkittler2018-11-26

Actions
Actions

Also available in: Atom PDF