Project

General

Profile

Actions
Copy link

action #12566

closed

The Worker Dies When the Job is Cancelled from GUI

Added by omaric almost 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
High
Assignee:
coolo
Category:
-
Target version:
-
Start date:
2016-06-30
Due date:
% Done:

0%

Estimated time:

Description

Sequence of Steps

  • The job that had been scheduled to run has appeared in GUI under "x jobs are running" section.
  • While it was still running, I cancelled it by using X (next to the Test name).

The Expected Outcome:

  • The worker should keep running and pick up the next scheduled jobs.

The Actual Outcome/Issue:

  • Cancelling the job had killed the worker.

Systemctl output:
systemctl status openqa-worker*
openqa-worker@1.service - openQA Worker #1
Loaded: loaded (/usr/lib/systemd/system/openqa-worker@.service; enabled)
Active: failed (Result: exit-code) since Thu 2016-06-30 11:20:17 CEST; 27s ago
Process: 12013 ExecStart=/usr/share/openqa/script/worker --instance %i (code=exited, status=1/FAILURE)
Process: 12010 ExecStartPre=/usr/bin/install -d -m 0755 -o _openqa-worker /var/lib/openqa/pool/%i (code=exited, status=0/SUCCESS)
Main PID: 12013 (code=exited, status=1/FAILURE)

The output from _openqa_worker:
job-working-directory: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
got job 70: 00000070-sle-4.0-x86_64-Build001-suma3@12_SP1_gnomeOnly
12052: WORKING 70
killing 12052
setting job 70 to incomplete (cancel)
can't open /var/lib/openqa/pool/1/testresults/result-consoletest_setup.json: No such file or directory at /usr/share/openqa/script/../lib/OpenQA/Worker/Jobs.pm line 529.
cleaning up 00000070-sle-4.0-x86_64-Build001-suma3@12_SP1_gnomeOnly...
QEMU (12060 -> /usr/bin/qemu-system-x86_64) should be dead - WASUP?

Related issues 1 (0 open — 1 closed)

Related to openQA Project - action #12178: worker can hang when killing isotovideoResolvedcoolo2016-05-31

Actions
Actions
Copy link

Also available in: Atom PDF