-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] [Distribution v1.13.1-rc1+WA982] Fails to extract OL1 / OL2 products generated by PUG #1028
Comments
Note: The error message is identical to error message in METADATA => [BUG] [Metadata v1.13.2-rc1] Fails to extract 1 specific SL_1 and 1 SL_2 product generated by PUG #1002 |
@Woljtek I couldn't find the mentioned products in the s3_pug index but only in the s3_l1_ntc index, so I assume that those products might be the ones you mentioned in this issue. Those products do contain a footprint in the index, so the workaround of #1002 was not applied. I could not find any specific discrepancy between the configuration of the mappings for the coordinates so I am a bit lost, as to why ES allows the footprint in the s3_l1_ntc but throws an error on the prip one. Could you provide the logs of the distribution-worker for further analysis? I could also add the workaround of #1002 again to the distribution-worker but the logs might help to understand what is happening here. |
IVV_CCB_2023_w28 : Moved into "Accepted Werum" for correction, Action on @Woljtek side : Please give logs about this issue. Priority blocking, to be fixed phase 1 |
Werum_CCB_2023_w28 : Moved into "Product Backlog", waiting for logs from @Woljtek |
@w-jka |
@Woljtek Test scenario
This commands starts a single-node elasticsearch instance locally, which is afterwards available on localhost:9200.
These two commands create two indices,
When publishing the footprint on
When publishing the same footprint to What is happening? How can we change the algorithm? |
Documentation on how to perform a reindex of data from one index to another So in order to fix this issue one approach is:
|
Candidate for refusal |
Werum_CCB_2023_w30 : to be checked on ADS side : |
System_CCB_2023-w30 : The RS Core - Elasticsearch Configuration is in line with the proposed fixed since the version 1.5 . The issue is still present in OPS, but a deployment from scratch will not have the issue. Priority reduced to minor with status CHECKED. |
For information , this issue impacted also OL2 product
I update issue title |
Environment:
Distribution: 1.13.1rc-1 + WA982 (use develop for distribution-worker)
processing S3-PUG-NRT : 1.13.1-rc1
Current Behavior:
The distribution-worker fails to extract prip-metadata for:
Expected Behavior:
Distribution shall be able to publish all products
Steps To Reproduce:
Republish in compression-event the message related to once of the 4 OL1_EFR products. 001_1440_LN3_O_NR_004
Test execution artefacts (i.e. logs, screenshots…)
The current error is the following:
Bug Generic Definition of Ready (DoR)
Bug Generic Definition of Done (DoD)
The text was updated successfully, but these errors were encountered: