Project

General

Profile

Actions
Copy link

action #137006

closed

Maintenance bot re-schedules incident each time it runs job "schedule incident"

Added by pcervinka about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
livdywan
Category:
Bugs in existing tests
Target version:
openQA Project - Ready
Start date:
2023-09-26
Due date:
% Done:

0%

Estimated time:
Difficulty:
Tags:
maintenance, qem-bot

Description

There is incident 29529 fo SLE 12-SP5, which is scheduled each time when bot run its job for scheduling.

We can see it in job logs:

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

2023-09-26 04:16:20 INFO     openqa-cli api --host https://openqa.suse.de -X post isos DISTRI=sle VERSION=12-SP5 ARCH=x86_64 FLAVOR=Server-DVD-HPC-Incidents _ONLY_OBSOLETE_SAME_BUILD=1 _OBSOLETE=1 INCIDENT_ID=29529 __CI_JOB_URL=https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1857242 BUILD=:29529:pdsh RRID=SUSE:Maintenance:29529:307637 REPOHASH=1695020026 HPCM_TEST_ISSUES=29529 INCIDENT_REPO=http://download.suse.de/ibs/SUSE:/Maintenance:/29529/SUSE_Updates_SLE-Module-HPC_12_x86_64 _PRIORITY=60 __SMELT_INCIDENT_URL=https://smelt.suse.de/incident/29529 __DASHBOARD_INCIDENT_URL=http://dashboard.qam.suse.de/incident/29529
2023-09-26 04:16:34 INFO     Put to dashboard result 200, database id: 2052736

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

2023-09-26 05:15:49 INFO     openqa-cli api --host https://openqa.suse.de -X post isos DISTRI=sle VERSION=12-SP5 ARCH=x86_64 FLAVOR=Server-DVD-HPC-Incidents _ONLY_OBSOLETE_SAME_BUILD=1 _OBSOLETE=1 INCIDENT_ID=29529 __CI_JOB_URL=https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/1857323 BUILD=:29529:pdsh RRID=SUSE:Maintenance:29529:307637 REPOHASH=1695020026 HPCM_TEST_ISSUES=29529 INCIDENT_REPO=http://download.suse.de/ibs/SUSE:/Maintenance:/29529/SUSE_Updates_SLE-Module-HPC_12_x86_64 _PRIORITY=60 __SMELT_INCIDENT_URL=https://smelt.suse.de/incident/29529 __DASHBOARD_INCIDENT_URL=http://dashboard.qam.suse.de/incident/29529
2023-09-26 05:16:03 INFO     Put to dashboard result 200, database id: 2052736
Actions
Copy link
 #1

Updated by pcervinka about 1 year ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by pcervinka about 1 year ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by pcervinka about 1 year ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by livdywan about 1 year ago

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

There's a proposed fix so I assume @osukup is working on that https://github.com/openSUSE/qem-bot/pull/141 (if it turns out he can't we can always unassign ofc)

Actions
Copy link
 #6

Updated by livdywan about 1 year ago

https://github.com/openSUSE/qem-bot/pull/142/files Looking to see if we can deduplicate since we have two versions of the same logic in the code

Actions
Copy link
 #7

Updated by livdywan about 1 year ago

  • Status changed from In Progress to Feedback
  • Assignee changed from osukup to livdywan

livdywan wrote in #note-6:

https://github.com/openSUSE/qem-bot/pull/142/files Looking to see if we can deduplicate since we have two versions of the same logic in the code

Managed to write unit tests that are able to check the "unversioned" case, and got the changes merged. Fingers crossed!

Actions
Copy link
 #8

Updated by pcervinka about 1 year ago

Actions
Copy link
 #9

Updated by okurz about 1 year ago

  • Category set to Bugs in existing tests
  • Status changed from Feedback to Resolved
  • Target version set to Ready

https://github.com/openSUSE/qem-bot/pull/142 merged. Things look good. As there are no "steps to reproduce" or "acceptance criteria" in the ticket and based on a statement in Slack from pcervinka earlier today that the issue is fixed I assume that's all that's needed

Actions
Copy link

Also available in: Atom PDF