Project

General

Profile

Actions

action #156301

closed

[bot-ng] Pipeline failed / KeyError: 'priority' / execution took longer than 4h0m0s seconds

Added by livdywan 10 months ago. Updated 10 months ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
-
Start date:
2024-02-29
Due date:
% Done:

0%

Estimated time:

Description

Observation

https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/2327183

++ retry -r 30 -e -- ./qem-bot/bot-ng.py -c /etc/openqabot --token [MASKED] incidents-run
[...]
KeyError: 'priority'
Retrying up to 19 more times after sleeping 6144s …
2024-02-29 06:28:46 INFO     Bot schedule starts now
Traceback (most recent call last):
  File "./qem-bot/bot-ng.py", line 7, in <module>
    main()
  File "/builds/qa-maintenance/bot-ng/qem-bot/openqabot/main.py", line 32, in main
    sys.exit(cfg.func(cfg))
  File "/builds/qa-maintenance/bot-ng/qem-bot/openqabot/args.py", line 24, in do_incident_schedule
    bot = OpenQABot(args)
  File "/builds/qa-maintenance/bot-ng/qem-bot/openqabot/openqabot.py", line 24, in __init__
    self.incidents = get_incidents(self.token)
  File "/builds/qa-maintenance/bot-ng/qem-bot/openqabot/loader/qem.py", line 41, in get_incidents
    xs.append(Incident(i))
  File "/builds/qa-maintenance/bot-ng/qem-bot/openqabot/types/incident.py", line 23, in __init__
    self.priority = incident["priority"]
KeyError: 'priority'
Retrying up to 18 more times after sleeping 12288s …
ERROR: Job failed: execution took longer than 4h0m0s seconds

Suggestions

  • DONE Restart pipelines
  • Investigate if there is new data the bot is not handling correctly
  • Don't provoke timeouts with retrying on reproducible errors
  • Look into unit test coverage

Related issues 1 (0 open1 closed)

Related to QA (public) - action #155629: [spike][timeboxed:6h][qem-dashboard] Order blocked incidents by priority to allow reviewers to focus on higher prio incidents first size:SResolvedmkittler2024-02-19

Actions
Actions #1

Updated by livdywan 10 months ago · Edited

Unfortunately the error is reproducible and failed the same way in the retry: https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/2327744

Actions #2

Updated by livdywan 10 months ago

  • Description updated (diff)
Actions #3

Updated by livdywan 10 months ago

  • Description updated (diff)
Actions #4

Updated by jbaier_cz 10 months ago

  • Related to action #155629: [spike][timeboxed:6h][qem-dashboard] Order blocked incidents by priority to allow reviewers to focus on higher prio incidents first size:S added
Actions #5

Updated by jbaier_cz 10 months ago

Likely a regression introduced by https://github.com/openSUSE/qem-bot/pull/171

Actions #6

Updated by mkittler 10 months ago

  • Status changed from New to In Progress
  • Assignee set to mkittler
Actions #9

Updated by mkittler 10 months ago

  • Status changed from In Progress to Feedback
Actions #10

Updated by mkittler 10 months ago

  • Status changed from Feedback to Resolved

The jobs on https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs look still good so I'm considering this resolved.

Actions

Also available in: Atom PDF