action #158805
closedJob details on minion dashboard inaccessible, observed on both o3+osd
0%
Description
Observation¶
Details of jobs on the minion dashboard on osd don't expand anymore and there's error messages in the developer console in the browser.
Even direct links don't seem to reveal the details, for example: https://openqa.suse.de/minion/jobs?id=10901255
It seems like there was a UX change and the columns are different now.
Acceptance criteria¶
- AC1: Details of minion jobs can be revealed
Suggestions¶
- Lookup changes in dependencies related to Mojolicious
- Consider changes to how openQA and the web UI is built and deployed
- Cross-check o3 for reference - issue looks to be reproducible with the minion dashboard on o3
Files
Updated by okurz 8 months ago
- Tags changed from infra to reactive work
- Project changed from openQA Infrastructure (public) to openQA Project (public)
- Subject changed from Job details on minion dashboard inaccessible on osd to Job details on minion dashboard inaccessible, observed on both o3+osd
- Category changed from Regressions/Crashes to Regressions/Crashes
Updated by tinita 8 months ago · Edited
- Status changed from New to In Progress
- Assignee set to tinita
We need to update Minion 10.29:
https://metacpan.org/release/SRI/Minion-10.29/source/Changes#L5 - Fixed jQuery dependency.
Mojolicious 9.36 doesn't deliver jquery.js it anymore, Minion now does.
That means we need to link it in https://build.opensuse.org/project/show/devel:openQA
Updated by tinita 8 months ago · Edited
- Status changed from In Progress to Feedback
On o3 it was already automatically updated and the webui restarted. On osd I have to explicitly install it from devel:OpenQA:
# zypper in perl-Minion
Loading repository data...
Reading installed packages...
'perl-Minion' is already installed.
There is an update candidate for 'perl-Minion' from vendor 'obs://build.opensuse.org/devel:openQA', while the current vendor is 'openSUSE'. Use 'zypper install perl-Minion-10.290.0-lp155.2.1.noarch' to install this candidate.
Resolving package dependencies...
Nothing to do.
Did that now and restarted the webui.
All looks good again.
I wonder why none of our tests failed.
Updated by mkittler 8 months ago
We should check why none of our tests failed when Mojolicious was updated.
I don't think we have any tests that would check whether the Minion UI works. Considering UI changes in Minion should rather be tested by the testsuite of Minion itself this also makes normally sense. I guess I could add a simple test that would open the Minion page, do a simple assertion and also implicitly check for JavaScript errors (as we always do).
Considering we're already linking Mojolicious we should probably also always link Minion like @tinita just did. Those packages are just highly related so it makes sense to treat them the same.