[FOLIO-1825] Include platform-ERM modules in folio-snapshot/testing. Specifically, mod-agreements, mod-licenses, ui-agreements, ui-licenses (With associated UI dependencies) Created: 25/Feb/19 Updated: 03/Jun/20 Resolved: 08/Mar/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Ian Ibbotson (Use this one) | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||
| Sprint: | Core: Platform - Sprint 58 | ||||||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||||||||||||||
| Comments |
| Comment by Jakub Skoczen [ 27/Feb/19 ] |
|
Per Ian Ibbotson (Use this one), there's no need to load sample nor reference data for those modules. If reference/sample data should be provided for folio-snapshot/folio-testing the modules will load it on their own and honour the loadSample/loadReference init params. |
| Comment by Khalilah Gambrell [ 27/Feb/19 ] |
|
These ERM modules on folio-snapshot / testing is a dependency on several eholdings stories in progress. I will link applicable Q1 eholdings features to this task. |
| Comment by Wayne Schneider [ 06/Mar/19 ] |
|
Required changes pushed to platform-complete, folio-ansible, and folio-infrastructure. platform-erm repository updated to work with CI. Open question: how to handle versioning of platform-erm? |
| Comment by Wayne Schneider [ 06/Mar/19 ] |
|
ERM team has been made aware of versioning implications. PRs merged to master, running test builds on AWS. |
| Comment by Wayne Schneider [ 06/Mar/19 ] |
|
Build succeeds for folio-snapshot, but folio-testing reports: TASK [folio-ansible/roles/okapi-tenant-deploy : Post install list for deployment and enabling] ***
fatal: [10.36.1.195]: FAILED! => {"changed": false, "connection": "close", "content": "POST request for mod-agreements-1.0.4-SNAPSHOT.49 /_/tenant failed with Connection refused: /10.36.1.195:9171", "content_length": "109", "content_type": "text/plain", "msg": "Status code was 500 and not [200]: HTTP Error 500: Internal Server Error", "redirected": false, "status": 500, "url": "http://10.36.1.195:9130/_/proxy/tenants/diku/install?deploy=true&tenantParameters=loadReference%3Dtrue%2CloadSample%3DtrueloadReference%3Dtrue%2CloadSample%3Dtrue"}
I think this may be a race condition where mod-agreements is not fully up before Okapi hits the tenant interface. Dropped a line to Adam Dickmeiss and Ian Ibbotson (Use this one) for feedback. |
| Comment by Wayne Schneider [ 07/Mar/19 ] |
|
Issue can easily be recreated by invoking tenant install with deploy=true for mod-agreements on the snapshot-backend-core Vagrant VM. Created
|
| Comment by Wayne Schneider [ 08/Mar/19 ] |
|
The work on this issue is complete and reviewed. The issue regarding mod-agreements in folio-testing has been opened as
|