Skip to content

[BUG] [OPS] L0p execution OL_CR[0] execution without output #1077

@suberti-ads

Description

@suberti-ads

Environment:

  • Delivery tag:
  • Platform: OPS Orange Cloud
  • Configuration:
    S3 L0p v1.13.2
    S3 L0p v1.14.0

Traceability:

Current Behavior:
On july month there was 21 execution L0P OK without output and with missing elements.
(issue still occurred in v1.14.0 on august)

Expected Behavior:
for each granule input we should have one S3_L0 product generated

Steps To Reproduce:
Current 3% Production

Test execution artefacts (i.e. logs, screenshots…)
hereafter logs occurred for Granule S3A_OL_0_CR___G_20230701T213250_20230701T221717_20230701T234738_2667______________SVL_O_NR_OPE.ISIP
L0pCR0_MissingOutput.log

Whenever possible, first analysis of the root cause
Hereafter sample of input for processing
S3A_OL_0_CR___G_20230701T213250_20230701T221717_20230701T234738_2667______________SVL_O_NR_OPE.ISIP
S3A_TM_0_NAT____20230701T213116_20230701T231229_20230701T235436_6073_100_300______LN3_O_AL_002.SEN3
S3A_AX___FRO_AX_20230628T000000_20230708T000000_20230701T065403___________________EUM_O_AL_001.SEN3
S3A_SR_0_SRA__G_20230701T224133_20230701T225133_20230701T234834_0600______________SVL_O_NR_OPE.ISIP
S3A_TM_0_NAT____20230701T213116_20230701T231243_20230701T235450_6086_100_300______LN3_O_AL_002.SEN3
S3A_AX___OSF_AX_20160216T192404_99991231T235959_20220330T090651___________________EUM_O_AL_001.SEN3

On execution log it sems skip all input.

2023-07-02T00:05:49+00:00	2023-07-02T00:05:49.873928 s3-l0p-part1-execution-worker-v47-69dc59848-vdt2q IPF-0 06.14 [0000001038]: [W] Check Gaps: Fail checking ISP stream of data to be written in L0 product.
2023-07-02T00:05:49+00:00	2023-07-02T00:05:49.873914 s3-l0p-part1-execution-worker-v47-69dc59848-vdt2q IPF-0 06.14 [0000001038]: [E] L0 ISP check:: The number of ISPs to be written is 0.
2023-07-02T00:05:49+00:00	2023-07-02T00:05:49.873903 s3-l0p-part1-execution-worker-v47-69dc59848-vdt2q IPF-0 06.14 [0000001038]: [I] Stats :: Total Num ISPs:  N_total_isps=120.
2023-07-02T00:05:49+00:00	2023-07-02T00:05:49.873891 s3-l0p-part1-execution-worker-v47-69dc59848-vdt2q IPF-0 06.14 [0000001038]: [I] Stats :: OLCI ISPs discarded due to wrong OEU_ICM_MODE = 120.
2023-07-02T00:05:49+00:00	2023-07-02T00:05:49.873882 s3-l0p-part1-execution-worker-v47-69dc59848-vdt2q IPF-0 06.14 [0000001038]: [I] Stats :: Discarded ISPs:  N_discarded_ISPs=120 , N_duplicated_ISPs=0 , N_outofjo_ISPs=0.

then OL_0_CR_.bin finshish with code 127

2023-07-02T00:05:49+00:00	{"header":{"type":"LOG","timestamp":"2023-07-02T00:05:49.875879Z","level":"INFO","line":129,"file":"TaskCallable.java","thread":"pool-454-thread-1"},"message":{"content":"Ending task /usr/local/components/S3IPF_L0_06.14/bin/OL_0_CR_.bin with exit code 127"},"custom":{"logger_string":"esa.s1pdgs.cpoc.ipf.execution.worker.job.process.TaskCallable"}}

Why L0 ISP were skipped ?
Is it an issue on processing ?

Bug Generic Definition of Ready (DoR)

  • The affect version in which the bug has been found is mentioned
  • The context and environment of the bug is detailed
  • The description of the bug is clear and unambiguous
  • The procedure (steps) to reproduce the bug is clearly detailed
  • The tested User Story / features is linked to the bug if available
  • Logs are attached if available
  • A data set attached if available

Bug Generic Definition of Done (DoD)

  • the modification implemented (the solution to fix the bug) is described in the bug.
  • Unit tests & Continuous integration performed - Test results available - Structural Test coverage reported by SONAR
  • Code committed in GIT with right tag or Analysis/Trade Off documentation up-to-date in reference-system-documentation repository
  • Code is compliant with coding rules (SONAR Report as evidence)
  • Acceptance criteria of the related User story are checked and Passed

Metadata

Metadata

Assignees

No one assigned

    Labels

    CCBIssue for CCBS3Relative to Sentinel-3 RS AddonsbugSomething isn't workingipfopsTicket from ADS operation teampriority:majorSet the priority to major because the production is heavily impacted

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions