Project

General

Profile

Actions
Copy link

action #14902

closed

[tools]incomplete job with no log file -> uploading failed in autoinst-log.txt

Added by Katharina100 over 7 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
-
Start date:
2016-11-20
Due date:
% Done:

0%

Estimated time:

Description

observation

https://openqa.opensuse.org/tests/307966#: job is incomplete; no log file (autoinst-log.txt) uploaded

problem

H1. job uploading of autoinst-log.txt itself has an error and job becomes incomplete

workaround

retrigger job, should be sporadic

Related issues 1 (0 open — 1 closed)

Blocked by openQA Project - action #6564: (re-)add Job::worker_idResolvedmkittler2015-03-06

Actions
Actions
Copy link
 #1

Updated by coolo over 7 years ago

the failure to upload the log will be the reason it's incomplete

Actions
Copy link
 #2

Updated by okurz over 7 years ago

  • Subject changed from incomplete job with no log file to incomplete job with no log file -> uploading failed in autoinst-log.txt

certainly, but I guess we can do something about it. szarate also mentioned something similar he plans. Different ideas come to mind:

  1. At least for the upload_log of autoinst-log.txt try more than once
  2. Continuously update the content of autoinst-log.txt on the target during a job run (i.e. handle differently than logs from within SUT)
  3. At least record the worker host somewhere so that we could know where to start looking.
Actions
Copy link
 #4

Updated by okurz over 7 years ago

Actions
Copy link
 #5

Updated by okurz about 7 years ago

  • Category set to Feature requests
Actions
Copy link
 #6

Updated by coolo about 7 years ago

  • Status changed from New to Resolved

I claim PR 1053 fixed that.

Actions
Copy link
 #7

Updated by szarate about 7 years ago

Actually, oliver mentioned one example of this happening few days ago... but that's related to workers being killed thus not being able to upload anything. So yes, This one in particular was fixed by PR#1053

Points 2 and 3 of @okurz's comments should be fixed when log4perl thingie is up and running thorughly on openqa.

  1. Continuously update the content of autoinst-log.txt on the target during a job run (i.e. handle differently than logs from within SUT)
  2. At least record the worker host somewhere so that we could know where to start looking.
Actions
Copy link
 #8

Updated by coolo about 7 years ago

When the workers are killed, there is little we can do. Possibly the webui can create an artificial log file to mark such cases?

Actions
Copy link
 #9

Updated by okurz about 7 years ago

  • Assignee set to szarate

good idea. I assume you don't want to blindly upload a snippet from the worker journal as it could spill secret information?

Actions
Copy link
 #10

Updated by coolo about 7 years ago

What is Dead May Never Die

Actions
Copy link
 #11

Updated by asmorodskyi about 7 years ago

  • Status changed from Resolved to In Progress

Still reproduces https://openqa.suse.de/tests/757188. Reopen

Actions
Copy link
 #12

Updated by RBrownSUSE about 7 years ago

  • Subject changed from incomplete job with no log file -> uploading failed in autoinst-log.txt to [tools]incomplete job with no log file -> uploading failed in autoinst-log.txt
Actions
Copy link
 #13

Updated by szarate almost 7 years ago

  • Priority changed from Normal to Low
Actions
Copy link
 #14

Updated by szarate almost 7 years ago

  • Status changed from In Progress to Feedback
  • Assignee deleted (szarate)

I haven't worked on this for a while.

Actions
Copy link
 #15

Updated by coolo over 6 years ago

  • Status changed from Feedback to Resolved

As we worked out an 80% solution, let's keep the rest as #27120

Actions
Copy link

Also available in: Atom PDF