In GCP R3 M10 environment having trouble with Seismic DDMS and performing segy to zgy conversion
R3M10 GCP pre-ship environment Problem with Seismic DDMS and segy to zgy conversion
- Cannot create new subproject under odesprod tenant using sdutil
- Cannot access the file in the existing subproject (autotesting) that was created in M9
- When I create the new tenant using Seismic DDMS, I can retrieve the tenant using Seismic DDMS API, but when I try to list the subprojects under **odesprod **using sdutil, I get the message of permission denied (500)
Created a tenant (autotest) using Seismic DDMS API I can retrieve the created tenant using Seismic DDMS API
curl --location --request GET https://preship.gcp.gnrg-osdu.projects.epam.com/api/seismic-store/v3/tenant/autotest' \--header 'Content-Type: application/json'
--header 'data-partition-id: odesprod'
--header 'Authorization: Bearer eyJhbGciOiJSU…t8bNiR5lakLVEstpsSZA'
Response: { "esd": "odesprod.osdu-gcp.go3-nrg.projects.epam.com", "gcpid": "AutoTest_project_id", "default_acls": "users.datalake.admins@odesprod.osdu-gcp.go3-nrg.projects.epam.com", "name": "autotest" }
(sdutilenv) D:\OSDU\dev\seismic-store-sdutil-master>python sdutil ls sd://autotest --idtoken=%ID_TOKEN%** [500] 7 PERMISSION_DENIED: Permission denied on resource project AutoTest_project_id.**
Then when I try to create the new subproject e.g. (autotestkt) I run into access problem (403) (sdutilenv) D:\OSDU\dev\seismic-store-sdutil-master>python sdutil mk "sd://odesprod/autotestkt" "admin@odesprod.osdu-gcp.go3-nrg.projects.epam.com" "odesprod-openZgy-Legal-Tag-7851742" --idtoken=%ID_TOKEN%
[1] REGIONAL [2] MULTI_REGIONAL [3] NEARLINE [4] COLDLINE
Select the bucket storage class: 2
[1] ASIA [2] EU [3] US
Select the bucket storage location: 3
Registering the subproject autotestkt(tenant=odesprod) with admin@odesprod.osdu-gcp.go3-nrg.projects.epam.com as admin ... [403] workload-seismic-store-gcp@osdu-service-prod.iam.gserviceaccount.com does not have storage.buckets.create access to the Google Cloud project.
Also, when I try to access segy file listed in the existing autotesting subproject created in R3M9, I can list the files but I cannot access the files, I get the message invalid legal tag. (sdutilenv) D:\OSDU\dev\seismic-store-sdutil-master>python sdutil ls sd://odesprod/autotesting --idtoken=%ID_TOKEN%
raman-test/ ST10010ZC11_PZ_PSDM_KIRCH_FULL_T.MIG_FIN.POST_STACK.3D.JS-017536.3a81a4cf-82ff-4dfc-a7b8-203db5bd4940.zgy ST10010ZC11_PZ_PSDM_KIRCH_FULL_T.MIG_FIN.POST_STACK.3D.JS-017536.74cbacfc-9de0-4379-85c8-ea7a51a32f56.zgy ST10010ZC11_PZ_PSDM_KIRCH_FULL_T.MIG_FIN.POST_STACK.3D.JS-017536.segy ST10010ZC11_PZ_PSDM_KIRCH_FULL_T.MIG_FIN.POST_STACK.3D.JS-017536.segy.idx ST10010ZC11_PZ_PSDM_KIRCH_FULL_T.MIG_FIN.POST_STACK.3D.JS-017536.segy.idx.bin
(sdutilenv) D:\OSDU\dev\seismic-store-sdutil-master>python sdutil stat sd://odesprod/autotesting/ST10010ZC11_PZ_PSDM_KIRCH_FULL_T.MIG_FIN.POST_STACK.3D.JS-017536.segy --idtoken=%ID_TOKEN%
[404] [seismic-store-service] The legal tag 'odesprod-Wellbore-Legal-Tag-Test3816976' is not valid.
Also, when I try to perform segy to zgy conversion using the DAG, it fails with log message indicating that the legal is not valid.
[2022-02-14 22:53:25,652] {pod_launcher.py:149} INFO - SDFileReader::SDFileReader: Error opening sd file: [2022-02-14 22:53:25,653] {pod_launcher.py:149} INFO - SeismicStore::DatasetLock: Error executing an HTTP request [ HTTP 404, [seismic-store-service] The legal tag 'odesprod-Wellbore-Legal-Tag-Test3816976' is not valid. ] [2022-02-14 22:53:25,653] {pod_launcher.py:149} INFO - SDFileReader::SDFileReader: Error opening sd file: SeismicStore::DatasetLock: Error executing an HTTP request [ HTTP 404, [seismic-store-service] The legal tag 'odesprod-Wellbore-Legal-Tag-Test3816976' is not valid. ] [2022-02-14 22:53:26,897] {taskinstance.py:615} DEBUG - Refreshing TaskInstance <TaskInstance: Segy_to_zgy_conversion.segy-to-zgy 2022-02-14T22:51:40.800163+00:00 [running]> from DB [2022-02-14 22:53:26,943] {taskinstance.py:650} DEBUG - Refreshed TaskInstance <TaskInstance: Segy_to_zgy_conversion.segy-to-zgy 2022-02-14T22:51:40.800163+00:00 [running]> [2022-02-14 22:53:26,947] {base_job.py:227} DEBUG - [heartbeat]