Pre Shipping issueshttps://community.opengroup.org/osdu/platform/pre-shipping/-/issues2023-02-24T22:21:53Zhttps://community.opengroup.org/osdu/platform/pre-shipping/-/issues/58Could not find osdu_api.ini config file - Wistml Ingestion - Airflow DAG - R3M82023-02-24T22:21:53Zetienne peyssonCould not find osdu_api.ini config file - Wistml Ingestion - Airflow DAG - R3M8When energetics_xml_ingest DAG is triggered.
Entering the Running state gives the following error :
[2021-09-20 18:56:56,511] {pod_launcher.py:149} INFO - File "/usr/local/lib/python3.6/site-packages/osdu_api/clients/base_client.py"...When energetics_xml_ingest DAG is triggered.
Entering the Running state gives the following error :
[2021-09-20 18:56:56,511] {pod_launcher.py:149} INFO - File "/usr/local/lib/python3.6/site-packages/osdu_api/clients/base_client.py", line 57, in _parse_config
[2021-09-20 18:56:56,512] {pod_launcher.py:149} INFO - raise Exception('Could not find osdu_api.ini config file')
[2021-09-20 18:56:56,512] {pod_launcher.py:149} INFO - Exception: Could not find osdu_api.ini config file
More details here :
https://waa6f12562960aaa4p-tp.appspot.com/log?dag_id=Energistics_xml_ingest&task_id=witsml_parser_task&execution_date=2021-09-20T18%3A55%3A07%2B00%3A00Aliaksandr Ramanovich (EPAM)Aleksandr Spivakov (EPAM)Aliaksandr Ramanovich (EPAM)https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/72GCP Smoke test collection - Issue with Seismic DMS folder, requests2021-09-29T13:34:21ZDebasis ChatterjeeGCP Smoke test collection - Issue with Seismic DMS folder, requestsI reported authentication problem to @aliaksandr_ramanovich from Smoke Test collection.
After you authenticate (refresh token), requests from “Core Services” and Ingestion folders work fine.
But requests from any other folder (Dataset...I reported authentication problem to @aliaksandr_ramanovich from Smoke Test collection.
After you authenticate (refresh token), requests from “Core Services” and Ingestion folders work fine.
But requests from any other folder (Dataset, SeismicDMS) fail with 401-unauthorized.Aliaksandr Ramanovich (EPAM)Aliaksandr Ramanovich (EPAM)https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/59R3M8 - Commands with {{FILE_HOST}} do not work2021-09-23T15:38:23ZValery GinakR3M8 - Commands with {{FILE_HOST}} do not work## Summary
When trying command 7 in CSV Workflow or command 1 in Manifest Ingestion (both include {{FILE_HOST}}) the error (Error: getaddrinfo ENOTFOUND https) occurs
## Steps to reproduce
Run any command with {{FILE_HOST}}
/cc @ka...## Summary
When trying command 7 in CSV Workflow or command 1 in Manifest Ingestion (both include {{FILE_HOST}}) the error (Error: getaddrinfo ENOTFOUND https) occurs
## Steps to reproduce
Run any command with {{FILE_HOST}}
/cc @kateryna_kurach
/cc @Aliaksandr_Ramanovich1Aliaksandr Ramanovich (EPAM)Aliaksandr Ramanovich (EPAM)https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/123Manifest ingestion - GCP R3M9 {workflow URL} not found, when previously work...2022-08-23T12:47:20ZSteven EvansManifest ingestion - GCP R3M9 {workflow URL} not found, when previously worked for M9 smoke testsSummary
After successful token authorization, when running any of the R3M9 smoke test collections and trying the R3 validation reference data manifest ingestion, each process fails with the same error: getaddrinfo ENOTFOUND preship-asm....Summary
After successful token authorization, when running any of the R3M9 smoke test collections and trying the R3 validation reference data manifest ingestion, each process fails with the same error: getaddrinfo ENOTFOUND preship-asm.osdu-gcp.go3-nrg.projects.epam.com
Steps to reproduce
1. Refresh token for M9 environment
2. Run any of the smoke test collections i.e legal tag and step 01a - reference Data Ingestion (Facility Type) from the R3 Validation full based manifest ingestion collection - #29 from the platform validation repository in Gitlab
the following error will appear - getaddrinfo ENOTFOUND preship-asm.osdu-gcp.go3-nrg.projects.epam.com
Example Environment(Tenant)
R3M9
What is the current bug behavior?
As above. Collections fail to run
What is the expected correct behavior?
Collection to run and return a valid response
Relevant logs and/or screenshots -
![image](/uploads/4d7504192ef0ccb4dfe250c8c572c15b/image.png)
![image](/uploads/d25b22defbb523b69ea3c81c34c0434a/image.png)Aliaksandr Ramanovich (EPAM)Aliaksandr Ramanovich (EPAM)