Project

General

Profile

action #108869

Updated by livdywan about 2 years ago

## Motivation 
 See https://suse.slack.com/archives/C02D16TCP99/p1648110330160679 

 From Jozef Pupava 
 > There are updates with no aggregates or record in http://dashboard.qam.suse.de/blocked S:M:23303:267916 S:M:23302:267917 S:M:23311:267930 S:M:23085:267929 ... 
 http://dashboard.qam.suse.de/incident/23302 
 http://dashboard.qam.suse.de/incident/23303 
 http://dashboard.qam.suse.de/incident/23311 
 http://dashboard.qam.suse.de/incident/23085 (edited)  

 > There is some issue, bot is not running jobs on (I guess) resubmited updates ? 
 e.g. samba 
 https://openqa.suse.de/tests/overview?distri=sle&version=15-SP2&build=%3A23309%3Asamba&groupid=310 
 What is the staged status ? 
 http://dashboard.qam.suse.de/incident/23309 

 > chrony update was rejected by @Paolo Stivanin but looking on the HA test the update is not added there so the test didn't fail due to regression https://bugzilla.suse.com/show_bug.cgi?id=1194220#c32 
 https://openqa.suse.de/tests/8379382#settings 
 Below @Paolo Stivanin mentioned kernel S:M:23280:268126 (edited)  

 > Another case where aggregates are failing because there is update which was released 2 days ago! 
 https://openqa.suse.de/tests/8380595#step/zypper_ref/3 

 > Today's Todays run is worthless, does not contain new updates and is running with released updates, repos are deleted 
 I guess same for yesterday and maybe even days before. (edited)  

 ## Acceptance criteria 
 - **AC1:** It is known what existing workflows require without needing any new features (Existing workflows to schedule incident and aggregate tests are ok again) 
 * **AC2:** Potential new feature requests have been identified and documented in new tickets 

 ## Suggestions 
 * Could be related to, or a regression from #103701 / https://gitlab.suse.de/qa-maintenance/bot-ng/-/merge_requests/46 
 * Talk to jpupava, e.g. in the Slack discussion mentioned above 
 * Try to find out what is actually broken 
 * Try to separate regressions from new feature requests which should go into separate tickets 
 * Try to separate "something is missing" cases from "something is failing" cases

Back