[FOLIO-3031] Install mod-data-export-worker in the reference environments Created: 23/Feb/21  Updated: 03/Mar/21  Resolved: 03/Mar/21

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

Type: Story Priority: P2
Reporter: Aleksei Prokhorov Assignee: David Crossley
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: File ftt-117-okapi.log.gz    
Issue links:
Blocks
blocks FOLIO-3030 Install mod-data-export-spring in the... Closed
is blocked by FOLIO-3012 Install MinIO service in environments Closed
Relates
relates to FOLIO-3053 Configure mod-data-export-worker for ... Closed
relates to FOLIO-3040 Failure adding springway modules refe... Closed
Sprint: DevOps Sprint 109, DevOps Sprint 108
Development Team: FOLIO DevOps

 Description   

Please install mod-data-export-worker in the reference environments:  https://folio-snapshot.dev.folio.org , https://folio-testing.dev.folio.org and https://folio-snapshot-load.dev.folio.org .



 Comments   
Comment by David Crossley [ 26/Feb/21 ]

I did try today to add both mod-data-export-worker and mod-data-export-spring. However they failed to deploy. See FOLIO-3040 Closed .

See related comments at FOLIO-3030 Closed .

Comment by Aleksei Prokhorov [ 26/Feb/21 ]

David Crossley We have made changes in mod-data-export-spring and mod-data-export-worker. Please retry

Comment by David Crossley [ 27/Feb/21 ]

I did try again today with folio-testing-test Jenkins build. The situation is much improved. The mod-data-export-spring does now start properly (see FOLIO-3030 Closed ).

However the mod-data-export-worker does not deploy properly.

See the Okapi log attached at ftt-117-okapi.log.gz

Comment by Roman Leshchenko [ 01/Mar/21 ]

David Crossley

We think that we have found the reason why it fails on start. We use TestContainers to run embedded MinIO server and it requires to run Docker-in-Docker. You can find additional info here https://www.testcontainers.org/supported_docker_environment/continuous_integration/dind_patterns/ .
It should be fixed by adding '-v /var/run/docker.sock:/var/run/docker.sock' parameter to docker run command.
Is it possible to add the parameter?

We had to change docker user (from folio to root) to be able run testcontainers in docker.

Comment by Jakub Skoczen [ 02/Mar/21 ]

Roman Leshchenko testcontainers should not be used on reference environments like folio-snapshot. Consider these envs similar to a production environment. All infrastrcture is provided outside of the module. There's a ticket FOLIO-3012 Closed to provide the minIO dependency in the reference env. Please disable testcontainers launching for regular (non-test) code.

Comment by Aleksei Prokhorov [ 02/Mar/21 ]

Jakub Skoczen Now when we have an S3 bucket to use we do not need this embedded MinIO server.

David Crossley We have disable the embedded MinIO server so please try this module deployment again.

Comment by David Crossley [ 03/Mar/21 ]

Hooray. The folio-testing-test and folio-snapshot-test Jenkins builds were successful. So now infrastructure configuration changes have been merged.

Following today's reference environment daily builds, the mod-data-export-worker and mod-data-export-spring modules will be available.

Comment by David Crossley [ 03/Mar/21 ]

Done.

Comment by Wayne Schneider [ 03/Mar/21 ]

Unfortunately, without either MinIO or S3, mod-data-export-worker crashes on deploy. This means that it can't be included in the reference Vagrant boxes without further work. See FOLIO-3053 Closed .

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