action #108701
closed
Individual groups return 500 via group_overview route
Added by livdywan about 2 years ago.
Updated about 2 years ago.
Category:
Regressions/Crashes
Description
Observation¶
Apparently some groups, for instance https://openqa.suse.de/group_overview/219, can produce HTTP 500 server errors. Can because at the time of writing #108659#note-1 it did, and now it works.
The same seems to be true of the overview on https://openqa.suse.de/ which would say Unable to fetch build results. as a side effect of the group reporting an error.
#108659#note-2 also revealed a log message that suggests the code path is broken:
Mar 21 18:08:28 openqa openqa[15913]: [error] [tWelNRQVXNmi] Undefined subroutine &OpenQA::BuildResults::log_error called at /usr/share/openqa/script/../lib/OpenQA/BuildResults.pm line 64.
According to the audit log the job template was modified. However I can't see what changes were made.
- Copied from action #108659: t/22-dashboard.t fails in one step but overall test still succeeds, maybe Test::Warnings? added
- Status changed from New to Feedback
- Assignee set to tinita
The reason was: 6 jobs with a label:force_result:softfail:poo#108674 label ("softfail" vs. "softfailed"). I fixed the jobs.
e.g. https://openqa.suse.de/tests/8363829#comments
It was clear from the error location lib/OpenQA/BuildResults.pm line 64 that there must be jobs which have a result or state not matching the ones that are checked, so I did
select * from jobs where group_id = 219 and (state = 'done' and result not in ('passed', 'softfailed', 'failed', 'incomplete', 'timeout_exceeded', 'skipped', 'obsoleted', 'parallel_failed', 'parallel_restarted', 'user_cancelled', 'user_restarted'));
and found the jobs.
- Due date set to 2022-04-04
I also triggered a new deployment in https://gitlab.suse.de/openqa/osd-deployment/-/pipelines/345098 . Thanks for your diligent work and fast fix. I would say you already patched the original issue by fixing the comments but also improved openQA itself. Unless you can think of further immediate improvements that we should apply as part of this ticket I'd say you can resolve the ticket.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF