Project

General

Profile

Actions

action #89560

open

Add alert for blocked gitlab account when users are unable to save/commit needles

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

Status:
Workable
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
QA (public, currently private due to #173521) - future
Start date:
2021-03-05
Due date:
% Done:

0%

Estimated time:

Description

Motivation

See #89047 . As discussed in retrospective 2021-03-05 we had #89047 based on a user report, not an automatic alert which we should always have first

Acceptance criteria

  • AC1: Alert exists for "blocked openqa-pusher gitlab account"

Suggestions

  • Look into existing minion related alerts
  • Crosscheck existing alert levels
  • Potentially extend the openQA influxdb API endpoint to more explicitly tell about the types of minion jobs to fail
  • Ensure there is a grafana alert working based on above data to alert us if the gitlab needle openqa-pusher account would be blocked again

Related issues 2 (0 open2 closed)

Related to openQA Infrastructure (public) - action #80538: flaky and misleading alerts about "openQA minion workers alert" as well as "Minion Jobs alert"Resolvedmkittler2020-11-272021-04-14

Actions
Related to openQA Infrastructure (public) - action #61221: osd: unable to save needles, minion fails with "fatal: Unable to create '/var/lib/openqa/.../needles/.git/index.lock'"Resolvedokurz2019-12-20

Actions
Actions #1

Updated by okurz almost 4 years ago

  • Related to action #80538: flaky and misleading alerts about "openQA minion workers alert" as well as "Minion Jobs alert" added
Actions #2

Updated by okurz almost 4 years ago

  • Related to action #61221: osd: unable to save needles, minion fails with "fatal: Unable to create '/var/lib/openqa/.../needles/.git/index.lock'" added
Actions #3

Updated by okurz almost 2 years ago

  • Tags changed from alert, needle, minion, git to alert, needle, minion, git, infra
Actions

Also available in: Atom PDF