Open eroan-marie opened 1 year ago
@eroan-marie Based on the provided logs, it seems, that two identical SYN intervals with different creation times were provided to the IPF. I would assume, that this might be the root cause, why the processor ran into an error in the NetCDF library.
IVV_CCB_2023_w28 : Moved into "Accepted Werum" for correction, Priority blocking, seems similar as #1022, to be fixed phase 1
Werum_CCB_2023_w28 : Moved into "Product Backlog" to see if a fix can be provided without change the tasktable
@eroan-marie After further investigation this issue does not seem to be related to #1022. There are no duplicated input validation time frames. As the issue happens inside of the IPF logic, and is related to the NetCDF library, this issue is not fixable by Werum in its current state. Please refer to the IPF provider with the logs of the IPF.
Candidate for refusal.
Werum_CCB_2023_w30 : One hypothesis is that this could be a baseline issue. This is under test on ADS side.
After the test with a consistent baseline, we have exactly the same behavior. Issue is to be analysed by Werum
@SYTHIER-ADS Was this issue provided to the IPF provider? If yes, what was the answer to this issue?
The issue PSC-67 has been created on ESA side. We are waiting for feedback to go further.
This is clearly a limitation for the system.
PDGSANOM-14095 created
For information this issue occurred on both satellite
New occurrence 19 errors for SY_2_SYN products in PUG STC
[code 290] [exitCode 255] [msg Task /usr/local/components/PUG-3.48/bin/PUGCoreProcessor failed]
error
2024-04-12T01:20:31+00:00 2024-04-12T01:20:31.707479 s3-pug-stc-part1-execution-worker-v12-d7546576c-x6l6d PUG_SY_2_SYN 03.48 [0000000107]: [I] PUGCoreProcessor: Exiting with EXIT CODE: 255
2024-04-12T01:20:31+00:00 FATAL: All the product data unit generations exited in error!
2024-04-12T01:20:31+00:00 Size mismatching!2024-04-12T01:20:31.707379 s3-pug-stc-part1-execution-worker-v12-d7546576c-x6l6d PUG_SY_2_SYN 03.48 [0000000107]: [E] PUGCoreProcessor: [PUGCoreProcessor.C: execute:(359)] Unable to generate the required PDUs! --- acs::exCriticalException in PDUGenerator.C(270) from void acs::PDUGenerator::createPDUs() thread "" [139970633246912]
2024-04-12T01:20:31+00:00 acs::Netcdf4Copy::exNetcdf4CopyCriticalException in Netcdf4Copy.C(418) from static void acs::Netcdf4Copy::concatVars(const netCDF::NcVar&, const netCDF::NcVar&, netCDF::NcVar&, const size_t&) thread "unnamedThread" [139970183141120]
2024-04-12T01:20:31+00:00 caused by:
2024-04-12T01:20:31+00:00 Problem found during product data unit generation -> skipping to the next, if any ...
2024-04-12T01:20:31+00:00 acs::PDUGenerator::exPDUGeneratorException in (0) from thread "" [139970633246912]
For information PDGSANMO-14095 created
Environment:
Traceability:
Current Behavior:
IPF crashes while processing some S3A_SY_2_SYN products
Expected Behavior:
Processing should work fine
Steps To Reproduce:
Try processing several S3A_SY_2_SYN products and see error below
Test execution artefacts (i.e. logs, screenshots…) Tip: You can attach images or log files by dragging & dropping, selecting or pasting them. s3-pug-stc.log
Whenever possible, first analysis of the root cause
Bug Generic Definition of Ready (DoR)
Bug Generic Definition of Done (DoD)