action #109488

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

coordination #109641: [epic] qem-bot improvements

qem-bot - better logging

Added by osukup 3 months ago. Updated 2 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


As followup 5-Why's

-> many log lines with "ERROR" about missing repomd.xml -> turn to INFO

-> log message "WARNING: Missing product in /etc/openqabot" -> "DEBUG: Skipping obsolete openQABot config /etc/openqabot/bot.yml"

-> log message "DEBUG: Incident … does not have x86_64 arch in 12-SP3" -> so what? -> maybe we can simply remove that message and ignore that, or move to TRACE

-> log message "DEBUG: No channels in … for …" -> Can we put some hints to the readers there what it means or what they could check, e.g. is there no valid smelt_channel to openQA product mapping in metadata? Maybe incident is obsolete and should be closed, removed, etc.?

-> log message "NOT SCHEDULE:" -> lowercase and use "not scheduling"

-> log message "Project ... can't calculate repohash" -> would be useful to have a timestamp of last update from OBS

-> log message for aggregates "Posting ... jobs" is ambiguous or wrong, should be more like "Triggering ... openQA products" or similar, or "openqa isos post calls"

-> we found a problem with an exception as openQA API returns with 404 on post isos as a product is missing in openQA. This error is ignored and we continue the job. We should handle that better.

-> add a concluding log message after triggering tests, like "Triggering done ... jobs" or so.

Acceptance criteria:

  • AC1: better logs from qem-bot

Related issues

Related to QA - action #108944: 5 whys follow-up to Missing (re-)schedules of SLE maintenance tests size:MResolved2022-03-24


#1 Updated by osukup 3 months ago

  • Related to action #108944: 5 whys follow-up to Missing (re-)schedules of SLE maintenance tests size:M added

#2 Updated by cdywan 3 months ago

  • Description updated (diff)

#3 Updated by okurz 3 months ago

  • Priority changed from Normal to Low
  • Target version set to Ready

#4 Updated by okurz 3 months ago

  • Parent task set to #109641

#5 Updated by osukup 3 months ago

  • Assignee set to osukup

#6 Updated by osukup 3 months ago

  • Status changed from New to In Progress

#8 Updated by osukup 2 months ago

  • Status changed from In Progress to Resolved

merged and deployed

Also available in: Atom PDF