Project

General

Profile

Actions
Copy link

action #81206

closed

coordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues

coordination #80828: [epic] Trigger 'auto-review' and 'openqa-investigate' from within openQA when jobs incomplete or fail on o3+osd

Trigger 'openqa-investigate' from within openQA when jobs fail on osd

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

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Category:
Feature requests
Target version:
Ready
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Acceptance criteria

  • AC1: openqa-investigate is triggered on osd when jobs fails

Suggestions

  • Same as in #80830 but for osd
  • monitor impact on osd

Related issues 2 (0 open — 2 closed)

Related to openQA Project (public) - action #81859: openqa-investigate triggers incomplete sets for multi-machine scenariosResolvedmkittler2021-01-07

Actions
Copied from openQA Project (public) - action #80830: Trigger 'openqa-investigate' from within openQA when jobs fail on o3Resolvedokurz2020-12-08

Actions
Actions
Copy link
 #1

Updated by okurz about 4 years ago

  • Copied from action #80830: Trigger 'openqa-investigate' from within openQA when jobs fail on o3 added
Actions
Copy link
 #2

Updated by okurz about 4 years ago

  • Priority changed from Low to Normal

Trying out on osd with

env host=openqa.suse.de exclude_group_regex='.*(Development|Public Cloud|Released|Others|Kernel|Virtualization).*' /opt/os-autoinst-scripts/openqa-label-known-issues-and-investigate-hook
Actions
Copy link
 #3

Updated by openqa_review about 4 years ago

  • Due date set to 2021-01-04

Setting due date based on mean cycle time of SUSE QE Tools

Actions
Copy link
 #4

Updated by okurz about 4 years ago

have not encountered problem but config was reset, likely by salt. Making persistent with https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/420

Actions
Copy link
 #5

Updated by okurz about 4 years ago

many unexpected jobs were triggered. Apparently the git update cron job on osd did not work since 2020-12-08 as the directory belongs to root but the cron job runs as geekotest.

https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/422

Did SQL delete from jobs where test ~ ':investigate:' and state ~ 'scheduled'; to repair for currently scheduled ones. And for running ones to delete nested ones:

for i in $(openqa-cli api --osd jobs state=running | jq '.jobs | .[] | select(.test|test(":investigate:.*:investigate:")) | .id'); do openqa-cli api --osd -X delete jobs/$i ; done
Actions
Copy link
 #6

Updated by okurz almost 4 years ago

  • Related to action #81859: openqa-investigate triggers incomplete sets for multi-machine scenarios added
Actions
Copy link
 #7

Updated by okurz almost 4 years ago

  • Status changed from In Progress to Resolved

With https://openqa.suse.de/tests?match=:investigate: we can see that investigation jobs are triggered. There was some discussion in https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/425 and we disabled openqa-investigate for "Maintenance", based on feedback as visible in related tickets.

Actions
Copy link
 #8

Updated by okurz almost 4 years ago

  • Due date deleted (2021-01-04)
Actions
Copy link

Also available in: Atom PDF