Project

General

Profile

Actions

action #169144

open

coordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes

coordination #96263: [epic] Exclude certain Minion tasks from "Too many Minion job failures alert" alert

coordination #99831: [epic] Better handle minion tasks failing with "Job terminated unexpectedly"

Link to minion job from openQA job with waiting task

Added by tinita about 1 month ago. Updated 27 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
QA (public, currently private due to #173521) - future
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Motivation

When a job is waiting for a GruTask, e.g. https://openqa.opensuse.org/tests/4604726
State: scheduled, waiting for background tasks (id: 20718867, name: download_asset), created about 24 hours ago
then it's hard to find the corresponding minion job because the gru_task_id 20718867 is not searchable from the web interface.
In this case the minion job failed because of a sigterm Job terminated unexpectedly (exit code: 0, signal: 15) (we have #108980 for that). But in any case it should be possible to quickly find the minion job to be able to fix a problem.

Suggestions

  • @kraih said you can only search for notes key names in the webapi notes field, so instead of notes {"gru_id": 20718867} we should have {"gru_id_20718867": 1}, then we could link to a minion search query from the job. Of course there are several places relying on the current content of the notes. We could use both keys for a certain time.

Related issues 1 (1 open0 closed)

Copied from openQA Project (public) - action #108980: Better handle minion tasks failing with "Job terminated unexpectedly" - OpenQA::Task::Asset::DownloadNew2022-03-25

Actions
Actions #1

Updated by tinita about 1 month ago

  • Copied from action #108980: Better handle minion tasks failing with "Job terminated unexpectedly" - OpenQA::Task::Asset::Download added
Actions #2

Updated by livdywan about 1 month ago

  • Target version set to future
  • Start date deleted (2022-03-25)

This should probably go in Future. The epic already has a few other tickets.

Actions #3

Updated by tinita 27 days ago

  • Description updated (diff)
Actions

Also available in: Atom PDF