[FOLIO-2037] Vagrant testing/testing-backend builds failing Created: 23/May/19  Updated: 03/Jun/20  Resolved: 28/May/19

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

Type: Bug Priority: P3
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: Text File okapi.log    
Issue links:
Blocks
is blocked by OKAPI-738 Increase internal deploy/undeploy tim... Closed
Relates
relates to OKAPI-737 Cannot restart Okapi when mod-authtok... Closed
Sprint:
Development Team: Core: Platform

 Description   

Error message:

testing-backend: fatal: [default]: FAILED! => {"changed": false, "connection": "close", "content": "Timed out after waiting 30000(ms) for a reply. address: __vertx.reply.21, repliedAddress: http://10.0.2.15:9130/deploy", "content_length": "118", "content_type": "text/plain", "msg": "Status code was 400 and not [200]: HTTP Error 400: Bad Request", "redirected": false, "status": 400, "url": "http://10.0.2.15:9130/_/proxy/tenants/diku/install?deploy=true&tenantParameters=loadSample%3Dtrue%2CloadReference%3Dtrue"

Full build log: https://jenkins-aws.indexdata.com/job/Automation/job/folio-blackbox/2178



 Comments   
Comment by Wayne Schneider [ 23/May/19 ]

I was unable to reproduce the problem running the build_testing_backend Vagrant build from folio-ansible. I was able to reproduce running the packer build from the command-line. Why the error should occur when running the Ansible playbook from packer and not when running from Vagrant is quite mysterious to me. A few salient points:

  • New Okapi release (2.29.2) 2 days ago, before then we never saw this error.
  • The Okapi release involved a change to the deployment/discovery manager to use the event bus.
  • The testing builds use the /_/proxy/tenants/diku/install endpoint to deploy modules (this is the step that fails), while snapshot builds use the /_/discovery/modules endpoint (posting individual deployment descriptors).
  • The error message Timed out after waiting 30000(ms) for a reply. address: __vertx.reply.21, repliedAddress: http://10.0.2.15:9130/deploy sure looks like it refers to some of the code that changed in Okapi 2.29.2.

Okapi log ( okapi.log ) attached. Adam Dickmeiss, do you mind taking a look?

Comment by Wayne Schneider [ 23/May/19 ]

Pinning Okapi to v2.29.1, the build succeeds, so that is somewhat suggestive.

Comment by Adam Dickmeiss [ 27/May/19 ]

oh.. it's probably the OKAPI-737 Closed

Comment by Adam Dickmeiss [ 27/May/19 ]

Okapi 2.29.3 released.

Comment by Wayne Schneider [ 28/May/19 ]

Builds were successful overnight. Thanks, Adam Dickmeiss!

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