Environment:
- Delivery tag:
- Platform: OPS Orange Cloud
- Configuration:
PUG-STC 1.14.0-rc1
Traceability:
Current Behavior:
PUG-STC execution for product SY_2_SYN fall in error
[code 290] [exitCode 255] [msg Task /usr/local/components/PUG-3.48/bin/PUGPostProcessor failed]
Expected Behavior:
Production successfully done with nominal production input.
Steps To Reproduce:
Production 3%
Test execution artefacts (i.e. logs, screenshots…)
Execution logs:
pug-stc-post-core-JobOrder.131506.xml.log
Whenever possible, first analysis of the root cause
All issue were found on production with input SY_2_SYN
sample for joborder JobOrder.131506.xml
Product input :
"S3B_AX___FRO_AX_20230727T000000_20230806T000000_20230730T065449___________________EUM_O_AL_001.SEN3"
"S3B_SY_2_SYN____20230729T203841_20230729T204041_20230730T091811_0119_082_171______LN3_D_ST_002.SEN3"
"S3B_SY_2_SYN____20230729T203641_20230729T203841_20230730T093239_0119_082_171______LN3_D_ST_002.SEN3"
"JobOrder.131506.xml"
On log there was following issue during production
2023-07-30T15:21:22+00:00 {"header":{"type":"LOG","timestamp":"2023-07-30T15:21:22.400898Z","level":"INFO","line":129,"file":"TaskCallable.java","thread":"pool-35-thread-1"},"message":{"content":"Ending task /usr/local/components/PUG-3.48/bin/PUGPostProcessor with exit code 255"},"custom":{"logger_string":"esa.s1pdgs.cpoc.ipf.execution.worker.job.process.TaskCallable"}}
2023-07-30T15:21:22+00:00 2023-07-30T15:21:22.392721 s3-pug-stc-part1-execution-worker-v1-6d7567f956-ld27p PUG_SY_2_SYN 03.48 [0000000140]: [I] PUGPostProcessor: Exiting with EXIT CODE: 255
2023-07-30T15:21:22+00:00 FATAL: All the product data unit generations exited in error!
2023-07-30T15:21:22+00:00 must have size 1.2023-07-30T15:21:22.392605 s3-pug-stc-part1-execution-worker-v1-6d7567f956-ld27p PUG_SY_2_SYN 03.48 [0000000140]: [E] PUGPostProcessor: [PUGPostProcessor.C: execute:(367)] Unable to generate the required PDUs! --- acs::exCriticalException in PDUGenerator.C(270) from void acs::PDUGenerator::createPDUs() thread "" [140399911340224]
2023-07-30T15:21:22+00:00 acs::ManifestBuilderS3SynL1L2::ManifestBuilderS3SynL1L2Exception in ManifestBuilderS3SynL1L2.C(370) from virtual void acs::ManifestBuilderS3SynL1L2::writeSecondaryProductMetadata() thread "unnamedThread" [140399393896192]
2023-07-30T15:21:22+00:00 caused by:
2023-07-30T15:21:22+00:00 Problem found during product data unit generation -> skipping to the next, if any ...
2023-07-30T15:21:22+00:00 acs::PDUGenerator::exPDUGeneratorException in (0) from thread "" [140399911340224]
2023-07-30T15:21:22+00:00 2023-07-30T15:21:22.332761 s3-pug-stc-part1-execution-worker-v1-6d7567f956-ld27p PUG_SY_2_SYN 03.48 [0000000140]: [I] PUGPostProcessor: writeProduct DONE.
It seems to be an issue with input product.
i have 2 hypothesys:
- issue on preparation worker which not select good input
- Issue on SY_2_SYN production
Bug Generic Definition of Ready (DoR)
Bug Generic Definition of Done (DoD)
Environment:
PUG-STC 1.14.0-rc1
Traceability:
Current Behavior:
PUG-STC execution for product SY_2_SYN fall in error
Expected Behavior:
Production successfully done with nominal production input.
Steps To Reproduce:
Production 3%
Test execution artefacts (i.e. logs, screenshots…)
Execution logs:
pug-stc-post-core-JobOrder.131506.xml.log
Whenever possible, first analysis of the root cause
All issue were found on production with input SY_2_SYN
sample for joborder JobOrder.131506.xml
Product input :
On log there was following issue during production
It seems to be an issue with input product.
i have 2 hypothesys:
Bug Generic Definition of Ready (DoR)
Bug Generic Definition of Done (DoD)