action #44351
Updated by mkittler over 5 years ago
Currently at least 4 ipmi workers (openqaworker2:23/24/25/26) workers, openqaworker2:23/24/25/26 are stuck. in "developer" mode for unknown reason. They can not finish jobs or take new jobs for over a day and some even several days. Despite But the misleading message from the developer mode, this issue has nothing mode interface does not show up in webui, just msg shows "System is waiting for developer, connect to do openqaworker2 at port 116 with Shared mode (otherwise the developer mode. (The misleading message is also already fixed on latest master.) job might be cancelled)". 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: link: https://openqa.suse.de/tests/2272494 (openqaworker2), https://openqa.suse.de/tests/2278365 (grenache-1)