Actions
action #19924
closedjob was killed during manual investigation / interactive mode
Start date:
2017-06-20
Due date:
% Done:
0%
Estimated time:
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
Actions