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.
Category:
Feature requests
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
- Copied from action #80830: Trigger 'openqa-investigate' from within openQA when jobs fail on o3 added
- 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
- Due date set to 2021-01-04
Setting due date based on mean cycle time of SUSE QE Tools
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
- Related to action #81859: openqa-investigate triggers incomplete sets for multi-machine scenarios added
- Status changed from In Progress to Resolved
- Due date deleted (
2021-01-04)
Also available in: Atom
PDF