action #157135
Updated by okurz about 2 months ago
## Observation
As far as I know the representation of openQA job status on http://dashboard.qam.suse.de/blocked should auto-update based on AMQP events from https://openqa.suse.de but when a failed job is restarted I don't see those updates happening on http://dashboard.qam.suse.de/blocked until a new forced status update happens in the "sync aggregates" as scheduled from https://gitlab.suse.de/qa-maintenance/bot-ng/-/pipeline_schedules every 30m.
EDIT: I just saw some minutes later at 0815Z that a red box turned to blue for a job that was restarted at 0802Z. That was possibly because https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs/2380594 "sync aggregates" just finished.
## Acceptance criteria
* **AC1:** We ensured that openQA job status events over AMQP update the accordingly display on http://dashboard.qam.suse.de/blocked
* **AC2:** *Given* existing openQA results for a SLE maintenance incident in https://openqa.suse.de and on https://dashboard.qam.suse.de/blocked with at least one failed openQA job *When* all failed openQA jobs for that incident results are scheduled, e.g. by restarting or triggering a new job in the same scenario, but not yet running, e.g. triggered for testing purposes with an invalid WORKER_CLASS, *Then* https://dashboard.qam.suse.de/blocked and http://dashboard.qam.suse.de/incident/$incident MUST NOT show any failed openQA jobs
## Suggestions
* Look into log messages from the according "dashboard-amqp-watcher.service" systemd service running next to the dashboard that should capture all according actions
* Look at https://github.com/openSUSE/qem-dashboard/blob/main/lib/Dashboard/Command/amqp_watcher.pm
* Verify that the code works as intended and that we actually see events from openQA, etc.
* Verify that openQA job updates actually show up to users looking at the dashboard