Open suberti-ads opened 1 year ago
@suberti-ads We added a new parameter for this issue:
app.preparation-worker.pdu.config.<product_type>.minPDULengthThreshold=0.0
app.housekeep.pdu.config.<product_type>.minPDULengthThreshold=0.0
This parameter tries to merge (or drop if not possible) too short time intervals in order to prevent this issue. It will be included in the next delivery 1.14.0-rc2.
System_CCB_2023_w31: Delivered in the Processing Sentinel-3 v.14.0 (Refer to https://github.com/COPRS/processing-sentinel-3/releases/tag/1.14.0-rc2) and in the Processing Sentinel-1 v1.14.0 (Refer to https://github.com/COPRS/processing-sentinel-1/releases/tag/1.14.0-rc2) and in the Processing Common v1.14.0 (Refer to https://github.com/COPRS/production-common/releases/tag/1.14.0-rc2)
To be validated by IVV/OPS team.
System_CCB_2023_w31 : Moved into "Accepted Werum", and to validate, action done.
I don't find configuration in contents for pug-ntc in last delivery: v 1.14.0-rc-2: https://github.com/COPRS/processing-sentinel-3/blob/1.14.0-rc2/s3-pug-ntc/content/stream-parameters.properties develop branch: https://github.com/COPRS/processing-sentinel-3/blob/develop/s3-pug-ntc/content/stream-parameters.properties So i add workaround tag
We will add and test this workaround with 1.14.
System_CCB_2023_w31 : To be tested with 1.14.0 version
There is not any occurrence of this error after deployment of 1.14.0:
System_CCB_2023_w31 : Fixed, closed
I have bad news on this issue:
I don't understand why this issue has been closed (the workaround is still applied and not merged in branch) https://github.com/COPRS/processing-sentinel-3/blob/1.16.0/s3-pug-ntc/content/stream-parameters.properties
New occurence occured despite of this workaround To reproduce this issue you can seen https://github.com/COPRS/rs-issues/issues/1091 This issue is the same as https://github.com/COPRS/rs-issues/issues/1090 ( for PUG-NRT)
Environment:
Traceability:
Current Behavior: Some execution fall in error with following message:
It appears product sensing duration was very short for these products.
Expected Behavior:
Steps To Reproduce: Start 3% production or 24h00 test
Test execution artefacts (i.e. logs, screenshots…) Execution logs: PUG-NTC-joborder-120263.txt JobOrder: Job120263.txt Preparation log: s3-pug-ntc-part1-preparation-worker-v2-84f98487d-9hph5.log
Whenever possible, first analysis of the root cause sample for job 120263 Product which trigger production ==> S3B_SL_1_RBT__20230427T234045_20230427T235320_20230630T215052_0754_079_001____LN3_D_NT_002.SEN3
First error seen in logs:
So it try to generate a very short product:
This match with value found in preparation job:
So it seems to be an configuration issue hereafter our configuration preparation:
preparation log received product seen:
Bug Generic Definition of Ready (DoR)
Bug Generic Definition of Done (DoD)