[FOLIO-2616] Jenkins job folio-perf-test fails install second batch of modules Created: 26/May/20 Updated: 03/Jun/20 Resolved: 29/May/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | TBD |
| Reporter: | David Crossley | Assignee: | Hongwei Ji |
| Resolution: | Done | Votes: | 0 |
| Labels: | platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | CP: sprint 89 | ||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||
| Description |
|
The Jenkins job folio-perf-test utilises the set of modules from the daily folio-snapshot build. It installs these in two batches. The first batch ("installPayload with both reference and sample") is successful. The second batch ("installPayload without reference and sample") fails with the concise message "Response Code: HTTP/1.1 400 Bad Request". Ummm. |
| Comments |
| Comment by David Crossley [ 26/May/20 ] |
|
The second batch fails quickly. I added a sleep before the teardown to enable getting the Okapi log. That shows that the first mod-* module in the install batch does fail. That might not be anything specific to mod-agreements, but here is the last portion of the Okapi log: 07:53:50 ERROR HttpResponse
HTTP response code=400 msg=POST request for mod-agreements-2.3.0-SNAPSHOT.238 /_/tenant failed with 500: {"error":500,"message":"org.grails.datastore.mapping.core.exceptions.ConfigurationException:
DataSource not found for name [supertenant_mod_agreements] in configuration. ...
A bit more context in the attached log snippet. |
| Comment by Hongwei Ji [ 26/May/20 ] |
|
David Crossley, I see some errors in mod-agreement log and opened ERM-903: Migration scripts has hardcoded diku tenant |
| Comment by Hongwei Ji [ 26/May/20 ] |
|
Opened another blocker issue: MODSOURMAN-318: Remove hardcoded diku tenant in db schema.json |
| Comment by David Crossley [ 28/May/20 ] |
|
Following the fixes for the abovementioned modules, the Jenkins job folio-perf-test did get further with enabling modules. However now it fails at mod-oai-pmh tenant init stage. I cannot glean any useful information from the logs, so perhaps Hongwei Ji can reveal. |
| Comment by Hongwei Ji [ 28/May/20 ] |
|
Looking into it. |
| Comment by Hongwei Ji [ 28/May/20 ] |
|
David Crossley the cause was permission related. The build job does not populate users till a later stage. To work around this chicken/egg issue, I made a change to skip auth-token check during the module install stage. This allows the build to finish. Hope this can unblock your other work. |
| Comment by David Crossley [ 29/May/20 ] |
|
Hooray, today's run of folio-perf-test now completes. Nice work Hongwei. And yes, that enables
|