Project

General

Profile

Actions
Copy link

action #103701

closed

coordination #91646: [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release

Resubmited incident (ID) with new release request (RR) inherits incident test results from previous RR

Added by dzedro about 3 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
osukup
Target version:
future
Start date:
2021-12-08
Due date:
% Done:

0%

Estimated time:

Description

When RR is declined it can be resubmitted with new RR.
Problem is that it's still same incident ID so it will have old results.
If the incident results passed then it can be auto-approved.
Regressions can pass trough.

e.g. S:M:21592:259811 http://dashboard.qam.suse.de/incident/21592

Files

Download all files
update.png (191 KB) update.png dzedro, 2021-12-08 11:53
rr.png (156 KB) rr.png dzedro, 2022-01-05 15:21

Related issues 5 (1 open — 4 closed)

Related to QA (public) - action #108869: Missing (re-)schedules of SLE maintenance tests size:MResolvedosukup2022-03-24

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

Actions
Related to QA (public) - action #119161: Approval step of qem-bot says incident has failed job in incidents but it looks empty on the dashboard size:MResolvedokurz2022-10-21

Actions
Related to QA (public) - action #123286: Bot and dashboard reference to wrong data and block update approval size:MResolvedkraih2022-12-21

Actions
Related to QA (public) - action #155206: [qem-bot] re-release update can miss repo and thus not schedule updatesNew2024-02-08

Actions
Actions
Copy link
 #1

Updated by dzedro about 3 years ago

  • Category set to Regressions/Crashes
Actions
Copy link
 #2

Updated by okurz about 3 years ago

  • Project changed from openQA Project (public) to QA (public)
  • Category deleted (Regressions/Crashes)
  • Target version set to future

When you say "Concrete Bugs", meaning a regression, can you reference a "last good"? Or is it actually a new feature request?

Actions
Copy link
 #3

Updated by dzedro about 3 years ago

I'm not aware of any regression, but it's flaw in bot which can cause regressions.
It's confusing, people can think result is based on latest submission, but must be not.
Can be called feature request.

Actions
Copy link
 #4

Updated by dzedro almost 3 years ago

Another example of old results being inherited from previous RR, there are just old test results or results don't exist anymore just the result statistics.
This is just annoying for reviewer and blocking auto-approve.
https://smelt.suse.de/incident/21598/

Actions
Copy link
 #5

Updated by osukup almost 3 years ago

yes, this is result of too simplified naming of INCIDENT by bot ( technical deept from past) ...

we need check where is used and change all places. (probadly MTUI + bot-ng + qem-dashboard

Actions
Copy link
 #6

Updated by osukup almost 3 years ago

another possibility is add variable ( for examle RRID) with RRID and then use this in approver part of bot, which unfortuanetly can work only for incidents part, not aggregates

Actions
Copy link
 #7

Updated by osukup almost 3 years ago

after code review .. it needs changes in bot-ng ( few lines) + in mtui (also should be simple)

Actions
Copy link
 #8

Updated by osukup almost 3 years ago

ahh , and I also forget about Template Generator (teregen)

Actions
Copy link
 #9

Updated by osukup almost 3 years ago

Ahh, I forgot .. there is problem...

We cant use RR ( review Request) because we start work on all incidents before are Review Requests created. ( Incidents in Staging Area)

@vpelcak, @dzedro .. any ideas ?

Actions
Copy link
 #10

Updated by dzedro almost 3 years ago

If we can't use RR then I don't know what options we have. Somehow drop previous results or filter results since day of new RR being submitted ?

Actions
Copy link
 #11

Updated by osukup almost 3 years ago

  • Status changed from New to In Progress
  • Assignee set to osukup
Actions
Copy link
 #12

Updated by osukup almost 3 years ago

  • Status changed from In Progress to Feedback

.. deployed, need check if it works as intended...

Actions
Copy link
 #13

Updated by osukup almost 3 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #14

Updated by okurz almost 3 years ago

  • Related to action #108869: Missing (re-)schedules of SLE maintenance tests size:M added
Actions
Copy link
 #15

Updated by okurz over 2 years ago

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

Updated by okurz over 2 years ago

  • Parent task set to #91646
Actions
Copy link
 #17

Updated by okurz about 2 years ago

  • Related to action #119161: Approval step of qem-bot says incident has failed job in incidents but it looks empty on the dashboard size:M added
Actions
Copy link
 #18

Updated by mgrifalconi almost 2 years ago

  • Related to action #123286: Bot and dashboard reference to wrong data and block update approval size:M added
Actions
Copy link
 #19

Updated by jbaier_cz 11 months ago

  • Related to action #155206: [qem-bot] re-release update can miss repo and thus not schedule updates added
Actions
Copy link

Also available in: Atom PDF