search

EOEPCA / rm-data-access

Data Access Service and Ingestion building block of the Resource Management domain area
Apache License 2.0
2 stars 4 forks source link

Issue with rm-data-access-registrar deployed using rm-data-access-core:1.2.6 #20

Open dineshbkumar06 opened 1 year ago

dineshbkumar06 commented 1 year ago

Initially the registrar failed to recognize http as source and this issue has been resolved with the patch https://gitlab.eox.at/vs/core/-/commit/07f7bab77a7a1ef3ae026b536abd54645c03ea3a by Fabian.

After the patch we redeployed, the rm-data-access harvester and registrar. Now we see that both modules are deployed properly with correct configuration files. The harvester, harvest and generates stac item for the file served by simple http server. The registrar now recognizes http as source and performs registration. But we notice some the following issues:

The registrar does not register the links to all the components (individual bands) of the product. Also the structure of the metadata does not look as it was with the version 1.2.5 catalog_issue

The http:// protocol for the files are replaced with S3:// registrar_issue_with_storage_protocol

While the output from the harvester reference the individual components properly: harvester_output

Could you please investigate this issue?

Thanks and regards, Dinesh Kumar Babu adwäisEO

rconway commented 1 year ago

Created issue EOEPCA-814.

kalxas commented 1 year ago

First of all it looks like you switched to the master version of the resource catalogue because I can see the stac extensions in your first screenshot. @dineshbkumar06 can you please confirm the image versions you are using?

kalxas commented 1 year ago

confirmed, the 1.2.6 release is broken, it is tagged from master instead of the 1.2.x branch. I am going to delete this release now

kalxas commented 1 year ago

New 1.2.6 release is published just now. It should fix the http issue and the metadata structure back to 1.2.5

dineshbkumar06 commented 1 year ago

Thank you for the quick fix. I will try the new release and let you know if everything is ok.

kalxas commented 1 year ago

This issue is now fixed in master branch. I will need to backport to 1.2.x and issue a new release

kalxas commented 1 year ago

@dineshbkumar06 please try the new 1.2.7 release for the registrar.

dineshbkumar06 commented 1 year ago

@kalxas yes sure, I will try the new version and let you know. Thank you.