action #114694
Updated by kraih over 1 year ago
## Observation Why does http://dashboard.qam.suse.de/incident/25171 show no aggregates? I assume this is why https://build.suse.de/request/show/276375 wasn't yet approved by qam-openqa. But for example https://openqa.suse.de/admin/productlog?id=952035 mentions the incident so aggregate openQA jobs do exist. Also see https://suse.slack.com/archives/C02AJ1E568M/p1658835230635849 ## Expected result * For every incident an entry should show up in https://dashboard.qam.suse.de * Every incident in https://dashboard.qam.suse.de incident + aggregate tests are triggered * Results from incident + aggregate tests show up on the dashboard * If there is a non-zero amount of related openQA jobs *and* none of them failed then qem-bot approves in IBS ## Acceptance criteria * **AC1:** There Aggregate tests show up for http://dashboard.qam.suse.de/incident/25171 in particular * **AC2:** Schedules are no more evaluated based on aggregate jobs missing for new incidents tests visible in http://dashboard.qam.suse.de/incident/25171 ## Suggestions - See if this could be a regression from recent clean-up (https://github.com/openSUSE/qem-dashboard/pull/78, https://github.com/openSUSE/qem-dashboard/pull/63) - Check existing logs for "Cleaning up old jobs for incident..." messages related to the incident (https://github.com/openSUSE/qem-dashboard/blob/af4e1672993265709f9d97a670d5653b9aef8903/lib/Dashboard/Model/Incidents.pm#L266) - Dashboard runs as service "dashboard" on qam2.suse.de, journal currently only contains data for about one day due to lots of HTTP request logging and small journal size - Maybe add more logging for cleanups to help with debugging similar cases in the future