[FOLIO-2983] Folio testing build failing - remote storage initialisation Created: 26/Jan/21  Updated: 17/Mar/21  Resolved: 27/Jan/21

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Marc Johnson Assignee: Viachaslau Khandramai (Inactive)
Resolution: Done Votes: 0
Labels: environments, outage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:
Development Team: Firebird

 Description   

Earlier today, the folio-testing build failed due to mod-remote-storage failing to be enabled for the diku tenant.

fatal: [10.36.1.11]: FAILED! => {"changed": false, "connection": "close", "content": "POST request for mod-remote-storage-1.0.1-SNAPSHOT.44 /_/tenant failed with 500: {\"timestamp\":\"2021-01-26T14:42:43.008+00:00\",\"status\":500,\"error\":\"Internal Server Error\",\"message\":\"\",\"path\":\"/_/tenant\"}", "content_length": "203", "content_type": "text/plain", "elapsed": 193, "msg": "Status code was 400 and not [200]: HTTP Error 400: Bad Request", "redirected": false, "status": 400, "url": "http://10.36.1.11:9130/_/proxy/tenants/diku/install?deploy=true&tenantParameters=loadSample%3Dtrue%2CloadReference%3Dtrue", "vary": "origin"}

The folio-testing build is currently failing with a different error error:

failed: [10.36.1.43] (item=[44, {'id': 'mod-orders-11.2.0-SNAPSHOT.386', 'name': 'Orders Business Logic Module', ....

Missing dependency: mod-orders-11.2.0-SNAPSHOT.386 requires finance.funds: 1.3. Missing dependency: mod-orders-11.2.0-SNAPSHOT.386 requires finance.transactions: 4.1. Missing dependency: mod-orders-11.2.0-SNAPSHOT.386 requires finance.order-transaction-summaries: 1.2. Missing dependency: mod-orders-11.2.0-SNAPSHOT.386 requires finance.ledgers: 1.5. Missing dependency: mod-orders-11.2.0-SNAPSHOT.386 requires finance.budgets: 1.3", 

... "msg": "Status code was 400 and not [201]: HTTP Error 400: Bad Request", "redirected": false, "status": 400, "url": "http://10.36.1.43:9130/_/proxy/modules", "vary": "origin"}

The only change I can find that has been made to mod-orders since the last successful build is https://github.com/folio-org/mod-orders/pull/409/files, which adds a new module permission. This seems an unlikely cause of this issue.

I have repeated the builds for mod-orders and folio-testing in case there was corrupt data or this was an intermittent failure.

I've checked the environment build order in case finance came after orders, which it does not.

cc: David Crossley in case the overnight builds fail



 Comments   
Comment by Marc Johnson [ 26/Jan/21 ]

Hmm. I think a fix to mod-finance by Aliaksandr Pautau may have resolved the orders and finance related issues.

However, there is now the return of the original build failure for mod-remote-storage

fatal: [10.36.1.5]: FAILED! => {"changed": false, "connection": "close", "content": "POST request for mod-remote-storage-1.0.1-SNAPSHOT.44 /_/tenant failed with 500: {\"timestamp\":\"2021-01-26T17:34:26.109+00:00\",\"status\":500,\"error\":\"Internal Server Error\",\"message\":\"\",\"path\":\"/_/tenant\"}", "content_length": "203", "content_type": "text/plain", "elapsed": 196, "msg": "Status code was 400 and not [200]: HTTP Error 400: Bad Request", "redirected": false, "status": 400, "url": "http://10.36.1.5:9130/_/proxy/tenants/diku/install?deploy=true&tenantParameters=loadSample%3Dtrue%2CloadReference%3Dtrue", "vary": "origin"}

Viachaslau Khandramai Please can this be investigated.

It might be caused by build 45 not being picked up yet.

Comment by Marc Johnson [ 26/Jan/21 ]

Viachaslau Khandramai

A little bit of further investigation (using the registry) has led me to discover why that is happening.

Build 42 of mod-remote-storage changes the version to 1.0.1 and build 45 reverts it to 1.0.0. Unfortunately, this means that build 45 and later won't be used in the hosted environment builds due to how Okapi determines the latest version of a module.

To resolve this, the version number of mod-remote-storage needs to be incremented to 1.0.1 or higher. As the mainline builds of modules are not intended to include patch version builds, I suggest changing it to 1.1.0.

{
"id": "mod-remote-storage-1.0.0-SNAPSHOT.45",
"name": "Remote storage API module"
},
{
"id": "mod-remote-storage-1.0.1-SNAPSHOT.42",
"name": "Remote storage API module"
},
{
"id": "mod-remote-storage-1.0.1-SNAPSHOT.43",
"name": "Remote storage API module"
},
{
"id": "mod-remote-storage-1.0.1-SNAPSHOT.44",
"name": "Remote storage API module"
},
Comment by Adam Dickmeiss [ 26/Jan/21 ]

The morale is: do NOT change the version in a POM file unless you are making a release.

Comment by Viachaslau Khandramai (Inactive) [ 26/Jan/21 ]

Marc Johnson,

you are totally correct. Thank you for assistance! I think this story can be closed as done because build successfully completed https://jenkins-aws.indexdata.com/job/FOLIO_Reference_Builds/job/folio-testing-backend/800/.

BR,
Slava

Comment by Marc Johnson [ 27/Jan/21 ]

Thanks Viachaslau Khandramai

Generated at Thu Feb 08 23:24:43 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.