Description of problem: Selecting "Show Results" in web UI displays "Internal error". Version-Release number of selected component (if applicable): Beaker 0.18.4 How reproducible: Unknown Steps to Reproduce: 1. Look at the following job: https://beaker.engineering.redhat.com/jobs/801440/ 2. Click on display results for any of the three recipes. Actual results: See attached pic Expected results: The recipe task results displayed. Additional info:
Created attachment 963771 [details] Beaker_BZ1169838
Paul, the problem is with the URL you are visiting. It has a trailing slash. https://beaker.engineering.redhat.com/jobs/801440/ If you remove the trailing slash it will work: https://beaker.engineering.redhat.com/jobs/801440 This is the same as bug 1019860. TurboGears will happily serve up the same page either with or without a trailing slash, but relative links will be broken in one case or the other. In this case it is the relative URLs for the AJAX results loading. Flask handles this better by redirecting to the trailing slash URL if appropriate.
Dan, assuming the results reporting update happens for Beaker 20, I'm guessing this will be converted to Flask at that point?
(In reply to Dan Callaghan from comment #2) > Paul, the problem is with the URL you are visiting. It has a trailing slash. > > https://beaker.engineering.redhat.com/jobs/801440/ > > If you remove the trailing slash it will work: > > https://beaker.engineering.redhat.com/jobs/801440 > > This is the same as bug 1019860. TurboGears will happily serve up the same > page either with or without a trailing slash, but relative links will be > broken in one case or the other. In this case it is the relative URLs for > the AJAX results loading. Flask handles this better by redirecting to the > trailing slash URL if appropriate. Apologies - Dan :/ Thank you for the explanation. Best, -pbunyan
This is "fixed" by the new job page implementation in bug 1263917, in the sense that accidentally visiting /jobs/1234/ (with trailing slash) will give you a 404 page.
(In reply to wangdong from comment #7) Ahhh that's an unintended consequence of the user pref we put in for opting out of the new job page. We are going to need to add some code to explicitly handle this I think, since this new behaviour is even worse than the original problem described in comment 2.
http://gerrit.beaker-project.org/4814
Beaker 23.0 has been released.