Project

General

Profile

Actions

action #155689

closed

bot-ng pipelines fails to schedule incidents

Added by nicksinger 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Tags:

Description

Observation

Since Feb 19, 2024 6:03pm GMT+0100 our pipelines in bot-ng fail at the step "schedule incidents": https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs e.g. https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/2292982 which was the first I could find

Acceptance Criteria

  • AC1: Pipelines do work again (complete the job "schedule incidents")

Rollback steps

Suggestions

  • Check if something changed
  • Read the logs and try to understand if the issues are the same and if/how we can fix them
Actions #1

Updated by okurz 4 months ago

  • Description updated (diff)
  • Due date deleted (2023-11-08)
  • Start date deleted (2023-10-23)
Actions #2

Updated by okurz 4 months ago

  • Priority changed from Urgent to Immediate
Actions #3

Updated by tinita 4 months ago

  • Status changed from New to In Progress
  • Assignee set to tinita
Actions #4

Updated by tinita 4 months ago

  • Priority changed from Immediate to High

We decided in a collab session what we should do to handle products with a null value for packages:
https://github.com/openSUSE/qem-bot/pull/167 Handle empty value for "packages" entry

Pipeline running now: https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/2296039

Introduced in this MR:
https://gitlab.suse.de/qa-maintenance/metadata/-/merge_requests/1002/diffs#ca77db4a18ffee4a8692b735f7d2fb1e61eb64ba_45_58

Actions #5

Updated by tinita 4 months ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF