Actions
action #97508
closedcoordination #102915: [saga][epic] Automated classification of failures
coordination #166655: [epic] openqa-label-known-issues
openqa-label-known-issues not triggered correctly on o3 size:S
Description
Observation¶
From https://matrix.to/#/!ilXMcHXPOjTZeauZcg:libera.chat/$tqPQuYHDbeR_QPcHKG89sFfF4OcB4kM-X8lDey3a0Qk https://openqa.opensuse.org/tests/1885536 should have triggered openqa-label-known-issues putting #96605 on the job and retrigger.
$ echo https://openqa.opensuse.org/tests/1885536 | dry_run=1 ./openqa-label-known-issues
openqa-cli api --host https://openqa.opensuse.org -X POST jobs/1885536/comments text=poo#96605 [migration] Increased number of incomplete jobs auto_review:"Migrate to file failed, it has been running for more than 240 seconds":retry
openqa-cli api --host https://openqa.opensuse.org -X POST jobs/1885536/restart
shows that the ticket would match but no label was put on the openQA jobs. https://openqa.opensuse.org/minion/jobs?id=733901 looks like a successfully triggered hook script for another job.
From gru logs:
Aug 25 01:30:13 ariel openqa-gru[15198]: /opt/os-autoinst-scripts/_common: line 40: echo: write error: Broken pipe
Aug 25 01:30:13 ariel openqa-gru[15198]: /opt/os-autoinst-scripts/_common: line 40: /usr/bin/tail: Permission denied
Expected result¶
openqa-label-known-issues should label (and retrigger) jobs on o3
Suggestions¶
- Look into minion jobs for hooks
- Look at gru logs on o3
- Check recent apparmor changes in salt
Actions