action #157204
Updated by okurz 10 months ago
## Motivation https://suse.slack.com/archives/C02CLB8TZP1/p1709892527534149?thread_ts=1709883106.021479&cid=C02CLB8TZP1 When openQA jobs are deleted then the according reference in qem-dashboard should also be removed. Listen to AMQP events to sync the removal accordingly ## Acceptance criteria * **AC1:** SLE maintenance openQA jobs previously blocking SLE maintenance updates on http://dashboard.qam.suse.de/blocked do not block approval after such openQA jobs are deleted from the openQA database ## Suggestions * Use TDD: Extend https://github.com/openSUSE/qem-dashboard/blob/main/t/amqp.t and ensure there is a failing test first * Extend https://github.com/openSUSE/qem-dashboard/blob/08cea810f936faeb6af35b645270d85f6569c6b9/lib/Dashboard/Model/AMQP.pm#L33 to update the database entry accordingly or delete, whatever is applicable * For all current openQA job result entries in the dashboard database crosscheck if there are entries for jobs that do not exist anymore in the openQA database. Remove accordingly. * Verify operation in production: E.g. create an artificial, failed openQA job in OSD for a non-critical SLE maintenance update, wait till it shows up as blocking on http://dashboard.qam.suse.de/blocked or in log files of the qem-bot "approve" cycle, remove the job over `openqa-cli -X delete jobs/$id` again and verify that http://dashboard.qam.suse.de/blocked does not show up as blocked on that job anymore ## Out of scope * Regular cleanup of results when we missed or have otherwise not received according AMQP events