Project

General

Profile

action #110629

QA - coordination #91646: [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release

coordination #91914: [epic] Make reviewing openQA results per squad easier

openqa-label-known-issues: Fallback notification address in openqa-label-known-issues if no email address could be parsed from group_overview

Added by okurz about 2 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-05-04
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Motivation

openqa-label-known-issues can inform about "unknown, to be reviewed issues". For this in #91605 we added support to send messages to configured email addresses in openQA job group descriptions. If no such email address is configured then we would loose the information about "unknown, to be reviewed issue". Instead we could, if configured, send a message to a "catch-all" address.

Acceptance criteria

  • AC1: Given a catch-all address configured, e.g. by environment variable configured in /etc/openqa/openqa.ini on the job done hook configuration line, When an unknown issue is encountered by openqa-label-known-issue And no email address could be parsed from the according openQA job group, Then send to the catch-all address instead
  • AC2: Given no catch-all address configured, When (as in AC1) Then the message about unknown issue is discarded (or logged)

Suggestions

  • Add elif branch to https://github.com/os-autoinst/scripts/blob/master/_common#L112= if catch-all address configured and send to that instead
  • Optional: Already configure catch-all addresses for o3 and/or osd, e.g. a dedicated mailing list or chat channel and inform people about that "triaging" channel. Every message to that channel would mean that the according openQA job should be reviewed and at least labeled accordingly and a proper communication target should be provided within the according job group

Related issues

Copied to openQA Infrastructure - action #110920: Emails from o3 are rejected by mx2.suse.de for certain sender/recipients size:SBlocked

History

#1 Updated by okurz about 2 months ago

  • Subject changed from auto-review: Fallback notification address in openqa-label-known-issues if no email address could be parsed from group_overview to openqa-label-known-issues: Fallback notification address in openqa-label-known-issues if no email address could be parsed from group_overview

#2 Updated by okurz about 2 months ago

  • Target version changed from future to Ready

#3 Updated by okurz about 2 months ago

  • Priority changed from Normal to High

#4 Updated by tinita about 2 months ago

  • Status changed from New to In Progress
  • Assignee set to tinita

#5 Updated by tinita about 2 months ago

  • Status changed from In Progress to Feedback

https://github.com/os-autoinst/scripts/pull/157 Allow fallback notification address for unknown issues

#6 Updated by okurz about 2 months ago

Awesome, merged. I suggest you create a dedicated Slack channel, configure it with an email address and put that into the OSD config, then announce it. This is gonna be awesome :)

#7 Updated by okurz about 2 months ago

Created https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/687 to add a fallback address within the OSD config pointing to a dedicated Slack room #discuss-openqa-auto-review-unknown-issues-osd

#8 Updated by okurz about 2 months ago

Messages in #discuss-openqa-auto-review-unknown-issues-osd show up just fine. As no messages were showing up anywhere before we configured the fallback address I see both AC1 and AC2 covered :) I have sent a message to https://suse.slack.com/archives/C02CANHLANP/p1652262823889619 as well

#9 Updated by okurz about 2 months ago

  • Due date set to 2022-05-25

#10 Updated by tinita about 2 months ago

  • Copied to action #110920: Emails from o3 are rejected by mx2.suse.de for certain sender/recipients size:S added

#11 Updated by tinita about 2 months ago

  • Status changed from Feedback to Resolved

For the email problems on o3 I created #110920

#12 Updated by okurz about 1 month ago

  • Due date deleted (2022-05-25)

Also available in: Atom PDF