Project

General

Profile

Actions

action #97508

closed

coordination #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

Added by okurz about 3 years ago. Updated about 1 month ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2021-08-25
Due date:
% Done:

0%

Estimated time:

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

Actions #1

Updated by livdywan about 3 years ago

  • Description updated (diff)
Actions #2

Updated by livdywan about 3 years ago

  • Description updated (diff)
Actions #3

Updated by livdywan about 3 years ago

  • Subject changed from openqa-label-known-issues not triggered correctly on o3 to openqa-label-known-issues not triggered correctly on o3 size:S
  • Status changed from New to Workable
Actions #4

Updated by mkittler about 3 years ago

  • Assignee set to mkittler
Actions #5

Updated by mkittler about 3 years ago

  • Status changed from Workable to In Progress
Actions #7

Updated by openqa_review about 3 years ago

  • Due date set to 2021-09-10

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

Actions #8

Updated by mkittler about 3 years ago

  • Status changed from In Progress to Feedback

Both PRs have been merged. Let's see whether it works on o3 after the next deployment. (Maybe a restart of the apparmor service or the machine is required.)

Actions #9

Updated by mkittler about 3 years ago

  • Status changed from Feedback to Resolved

Looks like it worked. I couldn't find any investigation-related errors in the logs anymore and investigation jobs show up under "All tests".

Actions #10

Updated by okurz about 1 month ago

  • Parent task set to #166655
Actions #11

Updated by okurz about 1 month ago

  • Due date deleted (2021-09-10)
Actions

Also available in: Atom PDF