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 size:S

Added by tinita 7 months ago. Updated about 12 hours ago.

Status:
Workable
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
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.

Acceptance Criteria

  • AC1: When an openQA job has a linked Gru Job, users can click on a link to see the corresponding minion job
  • AC2: When an openQA job does not have a linked Gru Job, there is no link to click on
  • AC3: When the corresponding minion job does not exist the webUI does not crash

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.
  • Link would look like: https://openqa.opensuse.org/minion/jobs?task=...&state=&queue=&note=gru_id_123
  • OpenQA::Shared::GruJob
  • OpenQA::Shared::Plugin::Gru
  • Migrating old minion job data into the new format is out-of-scope for this task

Related issues 1 (0 open1 closed)

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

Actions
Actions #1

Updated by tinita 7 months ago

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

Updated by livdywan 7 months 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 6 months ago

  • Description updated (diff)
Actions #4

Updated by okurz 2 months ago

  • Target version changed from future to Tools - Next
Actions #5

Updated by okurz 2 months ago

  • Subject changed from Link to minion job from openQA job with waiting task to Link to minion job from openQA job with waiting task size:S
  • Description updated (diff)
  • Status changed from New to Workable
Actions #6

Updated by okurz about 1 month ago

  • Priority changed from Normal to Low
Actions #7

Updated by okurz 22 days ago

  • Target version changed from Tools - Next to Ready
Actions #8

Updated by okurz about 12 hours ago

  • Target version changed from Ready to future
Actions

Also available in: Atom PDF