docker compose int-registry-batch-loader failure

[gxtchen]

🐛 Describe the bug identified during I&T

Trying to load Registry API with data following README from https://github.com/NASA-PDS/registry/blob/main/docker/README.md, docker-reg-api-integration-test-with-wait-1 exited with code 1 and no data was loaded

📜 To Reproduce

Steps to reproduce the behavior:

1. git clone https://github.com/NASA-PDS/registry.git
2. cd docker/certs
3. ./generate-certs.sh
4. cd ..
5. docker compose --profile=pds-core-registry up -d
6. docker compose --profile=int-registry-batch-loader up

registry-docker.log

🕵️ Expected behavior

docker-reg-api-integration-1 exited with code 0

⚙️ Engineering Details

[jordanpadams]

@gxtchen @viviant100 when creating issues you find during I&T, can we try to use the I&T Issue template? https://github.com/NASA-PDS/registry-api/issues/new/choose

[ramesh-maddegoda]

@gxtchen , thanks for reporting this!

I also executed the same steps you mentioned and noticed docker-reg-api-integration-test-with-wait-1 exited with code 1. However, that does not mean the data was not loaded. I think we should update the README file to check the following status to validate the successful test data load.

docker-registry-loader-test-init-1 exited with code 0

In the log file you shared, I noticed the the following message.

docker-registry-loader-test-init-1           | [SUMMARY] Elasticsearch URL: http://elasticsearch:9200, index: registry
docker-registry-loader-test-init-1           | [ERROR] Connection is closed

Was Elasticsearch/OpesnSearch URL is specified as http://elasticsearch:9200 (with HTTP) instead of https://elasticsearch:9200 (with HTTPS) in any of the configuration files?

[ramesh-maddegoda]

@gxtchen , also can you please delete the nasapds/registry-loader image in your local docker environment and allow the docker compose to pull the latest docker image of nasapds/registry-loader ?

[tloubrieu-jpl]

@gxtchen there are currently issues in the way the CICD generates the latest docker images. So I cannot see clearly what is causing the error that you are seeing in the automated integration tests.

I will try to generate a version 1.0.0 of the registry by tomorrow so that you can start the registry using the docker compose framework.

[tloubrieu-jpl]

Hi @gxtchen @viviant100 this issue is solved in the release 1.0.1 of the registry. The documentation is also published online for the docker compose deployment see https://nasa-pds.github.io/registry/install/docker-compose.html

I hope this helps. Let us know. Thanks

[viviant100]

@tloubrieu-jpl I&T is done with B12.1 registry I&T. Are you asking for another round of I&T testing for this particular release (1.0.1)?

[tloubrieu-jpl]

@viviant100 no I don't think we need to do one more round of testing. Sorry that was not ready for @gxtchen to work with the docker compose deployment but i am happy he was not blocked because of that.