Project

General

Profile

action #89560

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

Added by okurz 8 months ago.

Status:
Workable
Priority:
Low
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2021-03-05
Due date:
% Done:

0%

Estimated time:
Difficulty:

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

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

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

History

#1 Updated by okurz 8 months ago

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

#2 Updated by okurz 8 months 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

Also available in: Atom PDF