[FOLIO-3082] mod-password-validator failure in Vagrant builds Created: 18/Mar/21 Updated: 24/Mar/21 Resolved: 23/Mar/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | TBD |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | DevOps Sprint 110 |
| Development Team: | FOLIO DevOps |
| Description |
|
The last several "testing" Vagrant builds have failed with the error:
Deployment failed for service mod-password-validator-2.0.1-SNAPSHOT.35. Could not connect to 10.0.2.15:9139: finishConnect(..) failed: Connection refused: /10.0.2.15:9139
Running this build from Vagrant, I am unable to reproduce the error. We'll have to try running it from Packer and inspecting the VM when it fails. |
| Comments |
| Comment by Wayne Schneider [ 18/Mar/21 ] |
|
It appears that in the packer build, the module simply takes too long to come up. I can see in the Okapi log that it is still initializing (after more than 90 seconds) when Okapi gives up trying to connect. |
| Comment by Wayne Schneider [ 19/Mar/21 ] |
|
I think this has been fixed by setting Okapi's deploy.waitIterations system property to 90 (why it would take that long to boot up a module is beyond me!)...but I can't verify because the builds are now failing due to
|
| Comment by Wayne Schneider [ 23/Mar/21 ] |
|
In testing, setting this property resolves the issue. Closing this ticket. |