@manishk @todaiks As per the recent discussion (with Kamlesh) and further execution/analysis ....We are unable move forward in SeismicDMS api's using the AZURE Preshipping environment r3m8. It's only giving the response for the Legal Tag (New seismic store) and further the subsequent API's are ended up with 404 errors. The details of the results has been enclosed. Request you to kindly review the PPT and revert me with the possible solution. Azure_Preshipr3m8_Errors_in_SeismicDMS_Collection_1021.pdf
@manishk @Wibben @anujgupta @todaiks @ChrisZhang The Good thing is that, Seismic R3 collection is fully executed using the GCP-QA environment. However the same seismic collection on AWS & AZURE is ended up with errors at this particular requests. i.e 6b, 7b, 8b,9b, 10b. Before executing these API's, I got the finished status from 6a, 7a, 8a, 9a, 10a API's. Also reviewed the airflow dag files and unable to see Errors, Failures, Abort messages on the formed/ingested data. Kindly check the enclosed document & do the needful.AWS_SEISMIC_R3M8_QAENVI_CURL_Response_2109.docx
@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