Project

General

Profile

action #19924

job was killed during manual investigation / interactive mode

Added by okurz about 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Concrete Bugs
Target version:
-
Start date:
2017-06-20
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

observation

I started a job, went into interactive mode, halted the execution, connected over VNC, connected over telnet to the qemu monitoring port and called "cont" to continue execution. For some minutes I was on the machine and everything was fine. Then suddenly the VNC window closed and the qemu process was gone, the job was reported as incomplete without any logs. The corresponding worker journal:

Jun 20 11:11:02 openqaworker7 worker[29338]: [ERROR] 502 response: Proxy Error (remaining tries: 2)
Jun 20 11:11:07 openqaworker7 worker[29338]: [ERROR] 404 response: Not Found (remaining tries: 0)
Jun 20 11:11:07 openqaworker7 worker[29338]: [ERROR] Job aborted because web UI doesn't accept updates anymore (likely considers this job dead)
Jun 20 11:11:46 openqaworker7 worker[29338]: [ERROR] 404 response: Not Found (remaining tries: 0)
Jun 20 11:11:46 openqaworker7 worker[29338]: killed 9280
Jun 20 11:12:27 openqaworker7 worker[29338]: [INFO] registering worker with openQA http://openqa.suse.de...
Jun 20 11:12:27 openqaworker7 worker[29338]: [DEBUG] Either there is no job running or we were asked to stop: (1|Reason: api-failure)
Jun 20 11:12:27 openqaworker7 worker[29338]: [INFO] cleaning up 01010664-sle-12-SP3-Server-DVD-x86_64-Build0433-autoyast_error_dialog@64bit

expected result

job should not have been killed while in interactive mode, at least not before MAX_JOB_TIME


Related issues

Related to openQA Tests - action #20378: [tools]Too many 502 on openqaResolved2017-07-18

History

#1 Updated by EDiGiacinto almost 5 years ago

#2 Updated by EDiGiacinto almost 5 years ago

  • Status changed from New to In Progress
  • Assignee set to EDiGiacinto

Closing this bug since it might be related to #20378 which is now solved. Please re-open if problem still persist - in case it is persisting and the bug had attachments (such logs, screens, ecc.) please provide new ones.

#3 Updated by EDiGiacinto almost 5 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF