Project

General

Profile

Actions

action #155206

open

[qem-bot] re-release update can miss repo and thus not schedule updates

Added by dzedro 8 months ago. Updated 8 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
2024-02-08
Due date:
% Done:

0%

Estimated time:

Description

Re-release update is update of already released update for missing channels/targets.
Bot can fail to schedule update because of inconsistency between channels/targets and published repos.
In patchinfo can be channels/targets which is bot expecting to be published, but repo will be not published because it was published and released in previous update.
This does not happen often but when it happens then there are no tests scheduled.
In theory tests which run before should cover also this update which is same, just for another channels/targets.
So we can just manually approve the update or add workaround to make bot schedule this update despite the channels/targets and published repo inconsistency.
I would not automate this rare exception, just make possible to manually trigger tests for the update.

Example of such update
https://maintenance.suse.de/request/316566/ First update
https://maintenance.suse.de/request/319913/ Re-release of the first update

Two threads of this issue
https://suse.slack.com/archives/C02CANHLANP/p1705059696456929
https://suse.slack.com/archives/C02D16TCP99/p1707323276471179


Related issues 4 (2 open2 closed)

Related to QA - action #103701: Resubmited incident (ID) with new release request (RR) inherits incident test results from previous RRResolvedosukup2021-12-08

Actions
Related to QA - action #153886: SMELT incidents and Release Requests IDs are not unique and may interfere with update approval decisionNew2024-01-18

Actions
Related to openQA Project - action #109310: qem-bot/dashboard - mixed old and new incidents size:MResolvedkraih2022-03-31

Actions
Related to openQA Project - action #109974: qem-bot/dashboard - mixed old and new incidents - potential future ideasNew

Actions
Actions #1

Updated by okurz 8 months ago

  • Target version set to future
Actions #2

Updated by okurz 8 months ago

  • Tags set to qem-bot, maintenance, re-release, incident
  • Subject changed from [bot-ng] re-release update can miss repo and thus not schedule updates to [qem-bot] re-release update can miss repo and thus not schedule updates
Actions #3

Updated by jbaier_cz 8 months ago

  • Related to action #103701: Resubmited incident (ID) with new release request (RR) inherits incident test results from previous RR added
Actions #4

Updated by okurz 8 months ago

  • Related to action #153886: SMELT incidents and Release Requests IDs are not unique and may interfere with update approval decision added
Actions #5

Updated by jbaier_cz 8 months ago

  • Related to action #109310: qem-bot/dashboard - mixed old and new incidents size:M added
Actions #6

Updated by jbaier_cz 8 months ago

  • Related to action #109974: qem-bot/dashboard - mixed old and new incidents - potential future ideas added
Actions

Also available in: Atom PDF