[FOLIO-3025] Add mod-ebsconet to testing/snapshot hosted environments Created: 18/Feb/21 Updated: 04/Mar/21 Resolved: 04/Mar/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Story | Priority: | P3 |
| Reporter: | Max Shtanko | Assignee: | David Crossley |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||
| Sprint: | DevOps Sprint 109, DevOps Sprint 108 | ||||||||||||||||||||||||
| Development Team: | FOLIO DevOps | ||||||||||||||||||||||||
| Description |
|
There is a new mod-ebsconet (https://github.com/folio-org/mod-ebsconet) module that we'd like added to the hosted environments for testing and demo purposes. |
| Comments |
| Comment by David Crossley [ 22/Feb/21 ] |
|
I did try adding this to folio-testing-test build today, but Okapi failed to deploy it. Have you verified that mod-ebsconet can be deployed using a VM? Also see your setup ticket
|
| Comment by Max Shtanko [ 25/Feb/21 ] |
|
Hi David Crossley, I fixed all "api-lint" reported issues and successfully deployed using a VM locally. Can you please confirm that there are no pending issues from the development team (ThunderJet) is blocking the module to be deployed on the environments? Thank you. |
| Comment by David Crossley [ 26/Feb/21 ] |
|
I did try again today. However it failed to deploy. See
There was the same trouble with installing two other modules (
To assist with debugging
|
| Comment by Max Shtanko [ 26/Feb/21 ] |
|
Vagrant box version: 5.0.0-20210113.5664 |
| Comment by Victoria_Smelova [ 26/Feb/21 ] |
|
David Crossley Jakub Skoczen |
| Comment by David Crossley [ 27/Feb/21 ] |
|
I did try again today with folio-testing-test and folio-snapshot-test Jenkins builds. The situation is the same. It still does not start, and has the same "timeout" issue as described at
The developers of mod-data-export-spring had similar startup troubles. They made some code improvements, and now it does start properly (see
|
| Comment by Max Shtanko [ 02/Mar/21 ] |
|
Hi David Crossley, |
| Comment by David Crossley [ 02/Mar/21 ] |
|
Have you been successful with a local VM? For example with folio/snapshot-core |
| Comment by Max Shtanko [ 02/Mar/21 ] |
|
Yes. Maxs-MBP:testing-with-ui NorthWind$ vagrant box update ==> default: Checking for updates to 'folio/testing' default: Latest installed version: 5.0.0-20210113.5664 default: Version constraints: default: Provider: virtualbox ==> default: Updating 'folio/testing' with provider 'virtualbox' from version ==> default: '5.0.0-20210113.5664' to '5.0.0-20210301.5937'... ==> default: Loading metadata for box 'https://vagrantcloud.com/folio/testing' ==> default: Adding box 'folio/testing' (v5.0.0-20210301.5937) for provider: virtualbox default: Downloading: https://vagrantcloud.com/folio/boxes/testing/versions/5.0.0-20210301.5937/providers/virtualbox.box The version I tested was 5.0.0-20210113.5664. |
| Comment by David Crossley [ 02/Mar/21 ] |
|
As explained in
|
| Comment by David Crossley [ 02/Mar/21 ] |
|
Updated documentation to assist: |
| Comment by David Crossley [ 03/Mar/21 ] |
|
I did try yet again today. See attached logfile ftt-120-okapi.log.gz The issues are the same as before "Timed out after waiting 300000(ms) for a reply. address: __vertx.reply.42" |
| Comment by Max Shtanko [ 03/Mar/21 ] |
|
Hi David Crossley, I was able to successfully test the module locally with folio/snapshot-core recent, but I've encountered connection-refused issues with building the module as a Docker image. Can you please assist me with the current Dokerfile configuration? I made Dockerfile reconfiguration to keep as much similar to successfully deployed modules from your references. Regarding the error message you provided. I see several (in fact over 200) errors prior to the one you mentioned, including: And one more thing to take a closer look: This is the connection going to be ended with the timeout error and it starts from the very beginning of the log. What is trying to connect to the ebsconet module from the Okapi side as TenantManager and for what reason? |
| Comment by David Crossley [ 03/Mar/21 ] |
|
I am sorry, but it is not my job to assist with development, and i do not know enough to advise. There are many EPAM and EBSCO developers here, so you need to seek their assistance. |
| Comment by David Crossley [ 03/Mar/21 ] |
|
Regarding my request in the earlier Jira comment to verify that the module will install, enable, and deploy. That is not asking you to test your module code against the VM. Instead it is asking you to verify that your currently published module docker image will deploy without error using that VM. We at FOLIO DevOps cannot proceed until that is happening. I suggest that you follow those steps at https://dev.folio.org/guides/install-backend-module/#ensure-recent-local-vm Yes, obviously there is something wrong with your dockerised module. |
| Comment by David Crossley [ 03/Mar/21 ] |
|
Besides that, there is something else that is required. There needs to be an API endpoint that we can use to verify successful deployment, e.g. |
| Comment by Andrei Makaranka [ 03/Mar/21 ] |
|
Hi David Crossley , I found an issue in our configuration and successfully deployed the docker image "folioci/mod-ebsconet:1.0.0-SNAPSHOT.13" to the local vagrant box 'folio/snapshot-core'.
Could you please retry deployment of the mod-ebsconet? Thank you in advance.
Deployed logs : snapshot-core.txt Verification : mod-ebsconet-local-check.mp4
|
| Comment by David Crossley [ 03/Mar/21 ] |
|
Hooray, that is working with the folio-testing-test Jenkins build. Of course the health endpoint is not yet happening, but at least we get an error. That can come later. Late here, but i will proceed with the configuration and rebuilding of some reference environments. Good to have it in ASAP. |
| Comment by David Crossley [ 03/Mar/21 ] |
|
Are you able to say here on the ticket was the problem was? This could be a common mistake, and good to have a note here for seekers. And thanks for doing the local test. |
| Comment by Andrei Makaranka [ 03/Mar/21 ] |
|
Hi David Crossley, Great news, thanks The last issue was trivial - we missed port configuration on which our service need to be started. |
| Comment by Wayne Schneider [ 03/Mar/21 ] |
|
Note that FOLIO does not require the port to be 8081, you can also configure the port in the module descriptor template. Here is an example from mod-circulation. |
| Comment by David Crossley [ 03/Mar/21 ] |
|
Thanks Wayne. So yes they could simplify configuration. In this case the issue was that they had 8081 in ModuleDescriptor and Dockerfile, See pull/13 |
| Comment by David Crossley [ 03/Mar/21 ] |
|
Okay, so mod-ebsconet is now in folio-snapshot-load. The other reference environment builds will include it on tonight's normal daily runs. |
| Comment by David Crossley [ 04/Mar/21 ] |
|
There were delays in the reference environment builds today. But now all are re-built and mod-esconet is there. |