[FOLIO-1921] mod-erm-usage fails during tenant deployment Created: 28/Mar/19 Updated: 03/Jun/20 Resolved: 01/Apr/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P2 |
| Reporter: | Ian Hardy | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | devops, platform-backlog | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | Core: Platform - Sprint 60 | ||||||||
| Story Points: | 3 | ||||||||
| Development Team: | Core: Platform | ||||||||
| Description |
|
mod-erm-usage fails to deploy TASK [folio-ansible/roles/okapi-tenant-deploy : Post install list for deployment and enabling] ***
fatal: [10.36.1.47]: FAILED! => {"changed": false, "connection": "close", "content": "POST request for mod-erm-usage-2.1.0-SNAPSHOT.33 /_/tenant failed with PUT http://10.36.1.47:9170/usage-data-providers/0ba00047-b6cb-417a-a735-e2c1e45e30f1 returned status 500", "content_length": "175", "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.47:9130/_/proxy/tenants/diku/install?deploy=true&tenantParameters=loadSample%3Dtrue%2CloadReference%3DtrueloadSample%3Dtrue%2CloadReference%3Dtrue", "x_okapi_trace": "POST mod-authtoken-2.2.0-SNAPSHOT.44 http://10.36.1.47:9131/_/proxy/tenants/diku/install.. : 202 1550us"}
to retry, use: --limit @/home/jenkins/workspace/Automation/folio-testing-backend01-test/CI/ansible/folio-testing-backend.retry
|
| Comments |
| Comment by Wayne Schneider [ 29/Mar/19 ] |
|
In our testing, creating a new tenant and just installing mod-erm-usage (and its requirement, mod-vendors) does not fail. There is something about this particular configuration of modules and how they are posted to the tenant install endpoint that creates a condition that causes mod-erm-usage to respond to the tenant init with a 500 error. Okapi log: 2019-03-28 21:11:48,047 INFO DockerModuleHandle mod-erm-usage-2.1.0-SNAPSHOT.33 28 Mar 2019 21:11:48:046 INFO LogUtil [28369eqId] 172.17.0.1:50694 PUT /usage-data-providers/0ba00047-b6cb-417a-a735-e2c1e45e30f1 null HTTP_1_1 500 437 312 tid=diku Internal Server Error 2019-03-28 21:11:48,059 INFO DockerModuleHandle mod-erm-usage-2.1.0-SNAPSHOT.33 28 Mar 2019 21:11:48:058 WARN TenantLoading [28381eqId] PUT http://10.36.1.47:9170/usage-data-providers/0ba00047-b6cb-417a-a735-e2c1e45e30f1 returned status 500 mod-erm-usage log: 28 Mar 2019 21:11:48:032 INFO LogUtil [28355eqId] org.folio.rest.RestVerticle start invoking putUsageDataProvidersById 28 Mar 2019 21:11:48:046 INFO LogUtil [28369eqId] 172.17.0.1:50694 PUT /usage-data-providers/0ba00047-b6cb-417a-a735-e2c1e45e30f1 null HTTP_1_1 500 437 312 tid=diku Internal Server Error 28 Mar 2019 21:11:48:058 WARN TenantLoading [28381eqId] PUT http://10.36.1.47:9170/usage-data-providers/0ba00047-b6cb-417a-a735-e2c1e45e30f1 returned status 500 28 Mar 2019 21:11:48:060 INFO LogUtil [28383eqId] org.folio.rest.RestVerticle start invoking postTenant 28 Mar 2019 21:11:48:066 INFO LogUtil [28389eqId] 10.36.1.47:36396 POST /_/tenant null HTTP_1_1 500 104 2724 tid=diku Internal Server Error 28 Mar 2019 21:11:48:070 INFO LogUtil [28393eqId] org.folio.rest.RestVerticle start invoking putUsageDataProvidersById 28 Mar 2019 21:11:48:072 INFO LogUtil [28395eqId] 172.17.0.1:50722 PUT /usage-data-providers/00db3e61-e08e-4f8b-93ee-8e60fd402fc8 null HTTP_1_1 500 437 111 tid=diku Internal Server Error 28 Mar 2019 21:11:48:073 INFO LogUtil [28396eqId] org.folio.rest.RestVerticle start invoking putUsageDataProvidersById 28 Mar 2019 21:11:48:074 INFO LogUtil [28397eqId] 172.17.0.1:50726 PUT /usage-data-providers/9362de60-f8b2-4073-bee3-01fa5fc8462f null HTTP_1_1 500 437 102 tid=diku Internal Server Error 28 Mar 2019 21:11:48:075 INFO LogUtil [28398eqId] org.folio.rest.RestVerticle start invoking putUsageDataProvidersById 28 Mar 2019 21:11:48:076 INFO LogUtil [28399eqId] 172.17.0.1:50730 PUT /usage-data-providers/e67924ee-aa00-454e-8fd0-c3f81339d20e null HTTP_1_1 500 437 87 tid=diku Internal Server Error |
| Comment by Wayne Schneider [ 29/Mar/19 ] |
|
This situation is preventing us from deploying new "folio-snapshot" builds. We are continuing to build "folio-testing" by excluding mod-erm-usage and mod-erm-usage-harvester from the module list. |
| Comment by Wayne Schneider [ 29/Mar/19 ] |
|
Further testing shows that if mod-authtoken is enabled for the tenant before mod-erm-usage, tenant initialization fails, but if it is enabled after mod-erm-usage, initialization succeeds. I've raised
|
| Comment by Jakub Skoczen [ 01/Apr/19 ] |
|
Wayne Schneider is there an error message included in the 500 response? Is there anything in the logs that could indicate what the failure is related to (exceptions, stack traces)? |
| Comment by Wayne Schneider [ 01/Apr/19 ] |
|
Jakub Skoczen – no error messages were included in the logs, which I found a little strange. The ERM team believes they have identified the issue as a module permission issue, which they hope they have resolved in the latest snapshot release (currently being tested). |
| Comment by Wayne Schneider [ 01/Apr/19 ] |
|
snapshot build succeeded, running testing build now. |
| Comment by Wayne Schneider [ 01/Apr/19 ] |
|
Both snapshot and testing builds succeed now, and sample data are present. |