Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • I Ingestion Workflow
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Data Flow
  • Data IngestionData Ingestion
  • Ingestion Workflow
  • Issues
  • #125
Closed
Open
Issue created Aug 02, 2021 by Ananth T@ananth.lti6

Unable to Ingest the Seismic horizon data using the manifest ingestion dag : Osdu_ingest

@todaiks @ChrisZhang @ GCP & AWS clouds While working on the Seismic Horizon API, Refresh_Token was working fine. Similarly 10 (Post)-Ingestion Seismic Horizon record R3 and 10a (Get) Check the Seismic Horizon Workflow Status were executed normally. However at 10b (Post) Storage - Retrieve ingested Seismic Horizon Data record api was stopped due to 404- Record not found.

{ "code": 404, "reason": "Record not found", "message": "The record 'odesprod:work-product-component--SeismicHorizon:Auto_Test_999645280744' was not found" }

Further when checked on the airflow lag files, This "SeismicHorizon:Auto_Test_999645280744" was created in the before steps. But this was throwing error at 10b-Retrieve ingested Seismic Horizon Data record.

Two cloud platforms i.e GCP & AWS has given the errors at this level. The corresponding GCP Code Snippet and body response for the 10, 10a, 10b API's has been compiled and the document is enclosed. Kindly have the detailed review and revert us for the possible solution. Seismic_Horizon_Issue_GCP_020821.docx

Assignee
Assign to
Time tracking