OSDU Software issueshttps://community.opengroup.org/groups/osdu/-/issues2022-08-03T15:19:25Zhttps://community.opengroup.org/osdu/platform/consumption/geospatial/-/issues/134Testing - Add unit tests for transformer cache/sync logic2022-08-03T15:19:25ZJoel RomeroTesting - Add unit tests for transformer cache/sync logicAs a GCZ Developer, I want to add unit tests for the transformer cache/sync logic, so that I can ensure the code is working and catch any issues if changes are made.
**Acceptance Criteria**
- Unit tests added for transformer cache/sync ...As a GCZ Developer, I want to add unit tests for the transformer cache/sync logic, so that I can ensure the code is working and catch any issues if changes are made.
**Acceptance Criteria**
- Unit tests added for transformer cache/sync logic
- Unit tests run successfullyGCZ Sprint 20Bryan GunterBryan Gunterhttps://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/issues/50Follow-up from "Adding logs to track IT failure exception"2022-08-23T20:52:25ZYan Sushchynski (EPAM)Follow-up from "Adding logs to track IT failure exception"Hello.
The changes from !154 break integration test steps in CICD.
The following discussions from !154 should be addressed:
- [ ] @Yan_Sushchynski started a [discussion](https://community.opengroup.org/osdu/platform/system/reference/c...Hello.
The changes from !154 break integration test steps in CICD.
The following discussions from !154 should be addressed:
- [ ] @Yan_Sushchynski started a [discussion](https://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/merge_requests/154#note_124181):
> When `kwargs.get('callback')` returns None, this line of code will fail, because we can't concatenate string and `None`.
- [ ] @Yan_Sushchynski started a [discussion](https://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/merge_requests/154#note_124254):
> There will be the following error here:
> `TypeError: can only concatenate str (not "dict") to str`
>
> I'd recommend using this string-formatting approach:
> `f"All Header Params: {header_params}"`
- [ ] @Yan_Sushchynski started a [discussion](https://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/merge_requests/154#note_124255):
> Same as here: https://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/merge_requests/154#note_124254
- [ ] @Yan_Sushchynski started a [discussion](https://community.opengroup.org/osdu/platform/system/reference/crs-conversion-service/-/merge_requests/154#note_124258):
> If there is no `callback` and `params.get('callback')` returns `None`, this will throw `TypeError`.M12 - Release 0.15Aayushi JainAayushi Jainhttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/issues/57Fix storage integration tests when dynamic policies are used2022-11-02T13:47:00ZHrvoje MarkovicFix storage integration tests when dynamic policies are usedAWS reported broken integration tests and outdated documentation:
After enabling OPA on storage, I ran into a few issues while running the integration tests.
The instructions outlined here are outdated: https://community.opengroup.org...AWS reported broken integration tests and outdated documentation:
After enabling OPA on storage, I ran into a few issues while running the integration tests.
The instructions outlined here are outdated: https://community.opengroup.org/osdu/platform/system/storage/-/blob/master/docs/tutorial/PolicyService-Integration.md. The variable name should be: opa.opaEndpoint
I noticed that the OPA URL isn’t being passed to the OPA Service using the @ConfigurationProperties annotation. I don’t know if other CSP’s are having the same issue, but I replaced with @value to get this working for AWS; @ConfigurationProperties seems unnecessary since it’s not used for the other properties. I have an MR for this here: https://community.opengroup.org/osdu/platform/system/storage/-/merge_requests/425/diffs. Can you approve this change if it’s OK with you?
Additionally, I am still receiving 3 failing integration tests on Storage. After some investigation, I believe the errors are coming from the OPA validation; mostly due to incorrect HTTP codes being returned. Can you confirm? The failing tests are:
should_returnErrorCode400_when_anInvalidChildLegalTagProvided(org.opengroup.osdu.storage.legal.TestPopulateLegalInfoFromParentRecords)
java.lang.AssertionError: expected:<400> but was:<401>
should_deleteIncompliantLegaltagAndInvalidateRecordsAndNotIngestAgain_whenIncompliantMessageSentToEndpoint(org.opengroup.osdu.storage.PubsubEndpoint.TestPubsubEndpoint)
java.lang.AssertionError: expected:<400> but was:<201>
should_receiveHttp403_when_userIsNotAuthorizedToUpdateARecord(org.opengroup.osdu.storage.records.TestRecordAccessAuthorization)
java.lang.AssertionError: expected:<403> but was:<401>M14 - Release 0.17Kelly ZhouKelly Zhouhttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/issues/56Finalize and document Rego to Elastic DSL translate API2022-09-26T17:08:54ZHrvoje MarkovicFinalize and document Rego to Elastic DSL translate APIFinalize the API to translate Rego to Elastic DSL. This API will be used by search for dynamic evaluation of the policies.Finalize the API to translate Rego to Elastic DSL. This API will be used by search for dynamic evaluation of the policies.Shane HutchinsShane Hutchinshttps://community.opengroup.org/osdu/platform/security-and-compliance/policy/-/issues/55Integrate search with policy translate API2022-10-03T16:00:18ZHrvoje MarkovicIntegrate search with policy translate APISwitch search to use dynamic policies by using policy translate APISwitch search to use dynamic policies by using policy translate APIM14 - Release 0.17Maciej HanszkeShane HutchinsMaciej Hanszkehttps://community.opengroup.org/osdu/platform/system/lib/core/os-core-common/-/issues/60Changing info logs into debug logs2022-12-01T15:14:39ZNeha KhandelwalChanging info logs into debug logsIn the OSDU Storage service, we are incurring large costs due to info logs created every time a request is sent to the Entitlements service. These logs are being created in the class HttpClientHandler.java (line 110) and are of the forma...In the OSDU Storage service, we are incurring large costs due to info logs created every time a request is sent to the Entitlements service. These logs are being created in the class HttpClientHandler.java (line 110) and are of the format "method: %s | latency: %s | url: %s | correlation id: %s". Such logs can be turned into debug logs to save on costs. There are two reasons why this change is viable: the Entitlements service creates request logs whenever a request is received, and info logs will still be created in Storage if any error occurs with the request. If needed, the logs can be switched back to info logs in the future.Neha KhandelwalNeha Khandelwalhttps://community.opengroup.org/osdu/platform/system/indexer-queue/-/issues/14Lack of retries control in AbstractMessageHandler2022-08-11T08:49:34ZYauheni LesnikauLack of retries control in AbstractMessageHandlerIn AbstractMessageHandler whe have some retry mechanism, but the current implementation contains one drawback: after failing processing of the message we abandon the one and in this case we can't control repeated consumption and there is...In AbstractMessageHandler whe have some retry mechanism, but the current implementation contains one drawback: after failing processing of the message we abandon the one and in this case we can't control repeated consumption and there is high chance that message will be received immediate.
We are doing the thread sleep for exponential backoff behavior, but it is innaficient because thread appears busy during the sleeping time. On the other hand, we unable to control max delivery count from the code, because it is an attribute of the topic subscribtion, not our services.
Also there is a new reindex into the indexer service process which locks the particular kind during the re-indexing and this process can be really long running (hours). In this case all events for the locked kind will toward to the dead letter queue, if we don't have long term retry mechanism.
It would be good if we could have more control for retry behavior using service bus client infrastructure principally.Yauheni LesnikauYauheni Lesnikauhttps://community.opengroup.org/osdu/platform/system/file/-/issues/69File Service: Requests to POST metadata are taking long time2022-08-23T21:03:43ZSachin JaiswalFile Service: Requests to POST metadata are taking long time### Problem Statement
Request to post metadata takes long time when try to calculate the checksum for larger files.
### Solution
We can overcome this problem by reading bytes from the input stream and storing them into the buffer array.### Problem Statement
Request to post metadata takes long time when try to calculate the checksum for larger files.
### Solution
We can overcome this problem by reading bytes from the input stream and storing them into the buffer array.https://community.opengroup.org/osdu/data/data-definitions/-/issues/40Schema creation problem in R3M9 instance (cannot find parent entity although ...2022-06-08T00:46:05ZDebasis ChatterjeeSchema creation problem in R3M9 instance (cannot find parent entity although it is created)@gehrmann - Please note that when creating Wellbore 1.1.0 in R3M9/AWS instance (used for GCZ development team), I hit a problem with parent abstract entity. Could be because initially I created with slightly incorrect value of ID (entit...@gehrmann - Please note that when creating Wellbore 1.1.0 in R3M9/AWS instance (used for GCZ development team), I hit a problem with parent abstract entity. Could be because initially I created with slightly incorrect value of ID (entity.1.1.0 instead of entity:1.1.0). Second time, it shows "entity already exists". I can even search the schema entity. "AbstractanyCrsFeature:1.1.0"
[Schema1-AbstractAnyCRS.txt](/uploads/8466db4afdae088f7d21c89aada02f4d/Schema1-AbstractAnyCRS.txt)
But when it is used in json script of next entity (AbstractSpatial) it does not find and it fails.
[Schema2-AbstractSpatial.txt](/uploads/ff4b1b0b2534f651345a91d7bedddf12/Schema2-AbstractSpatial.txt)
One problem is that Schema service does not allow deletion.
Do you have any suggestion about going past this blocker?
Thank youhttps://community.opengroup.org/osdu/platform/data-flow/ingestion/ingestion-workflow/-/issues/147Update Status end point is publishing INGESTOR stage GSM messages2022-08-11T04:56:25Zdevesh bajpaiUpdate Status end point is publishing INGESTOR stage GSM messagesUpdate status endpoint in workflow service is publishing "INGESTOR"stage GSM messages. Workflow service update status endpoint can be called by user and this case "INGESTOR" stage in published GSM message doesn't seems valid. Workflow se...Update status endpoint in workflow service is publishing "INGESTOR"stage GSM messages. Workflow service update status endpoint can be called by user and this case "INGESTOR" stage in published GSM message doesn't seems valid. Workflow service can publish GSM message with "WORKFLOW" stage to give clear distinction regarding the source of GSM message.M13 - Release 0.16https://community.opengroup.org/osdu/platform/system/storage/-/issues/126All versions of a record have the same modifyUser and modifyTime2023-05-30T10:26:54ZAn NgoAll versions of a record have the same modifyUser and modifyTimeThe concept is that one record should have 1 version of metadata.
However, in regard to modifyUser and modifyTime attributes, they should be different for each version.
Currently, the behaviors are as implemented, but the behavior by th...The concept is that one record should have 1 version of metadata.
However, in regard to modifyUser and modifyTime attributes, they should be different for each version.
Currently, the behaviors are as implemented, but the behavior by the above concept is wrong.
So with the current behavior, for multiple versions of the same record modifyTime and modifyUser value are same and they are overwritten to all versions during every modification made to the record.
Which means for records having only 1 version, it is like below.
|version1|
|:-------|
|createUser|
|createTime|
But when the record is modified and multiple versions are created, the metadata of the record for latest version is applied to all versions including the first version as well, and all versions have value for modifyUser and modifyTime attributes.
|version1|version2 |version3|
|:-------|:--------|:--------|
|createUser| createUser| createUser|
|createTime| createTime| createTime|
|modifyUser2 |modifyUser2|modifyUser2|
|modifyTime2 |modifyTime2|modifyTime2|
**Expected:**
Version 1 should only have createUser and createTime. modifyUser and modifyTime should not exist in the first version.
Version 2+ should have different modifyUser and modifyTime for each version
|version1|version2 |version3|
|:-------|:--------|:--------|
|createUser| createUser| createUser|
|createTime| createTime| createTime|
| |modifyUser1|modifyUser2|
| |modifyTime1|modifyTime2|https://community.opengroup.org/osdu/data/data-definitions/-/issues/39Lack of any spatial information provided for TNO WellLog Records2022-06-07T10:25:10ZMichaelLack of any spatial information provided for TNO WellLog RecordsThe manifest records for the TNO work-product-component--WellLog lack any Spatial fields. This prevents any spatialFilter queries from being done on the well logs. The location information should be provided for the trajectories when ava...The manifest records for the TNO work-product-component--WellLog lack any Spatial fields. This prevents any spatialFilter queries from being done on the well logs. The location information should be provided for the trajectories when available because this allows users to filter well logsby location on a large scale without having to link a well log to its parent Wellbore or Well.https://community.opengroup.org/osdu/data/data-definitions/-/issues/38Lack of any spatial information provided for TNO WellboreTrajectory Records2022-06-07T10:26:05ZMichaelLack of any spatial information provided for TNO WellboreTrajectory RecordsThe manifest records for the TNO work-product-component--WellboreTrajectory lack any Spatial fields. This prevents any spatialFilter queries from being done on the trajectories. The location information should be provided for the traject...The manifest records for the TNO work-product-component--WellboreTrajectory lack any Spatial fields. This prevents any spatialFilter queries from being done on the trajectories. The location information should be provided for the trajectories when available because this allows users to filter trajectories by location on a large scale without having to link a trajectory to its parent Wellbore or Well.https://community.opengroup.org/osdu/platform/security-and-compliance/legal/-/issues/27Optimal memory and cpu configuration to stand against load2023-08-07T09:37:15ZRostislav Vatolinvatolinrp@gmail.comOptimal memory and cpu configuration to stand against loadPlease conduct load tests to see the optimal configuration for legal service in Azure environment.
Please update hpa and resources configuration.Please conduct load tests to see the optimal configuration for legal service in Azure environment.
Please update hpa and resources configuration.Rostislav Vatolinvatolinrp@gmail.comRostislav Vatolinvatolinrp@gmail.comhttps://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/122Unhandled exception from VolumeDataStoreIOManager::ReadChunkImpl()2022-08-09T09:57:58ZAlex TUnhandled exception from VolumeDataStoreIOManager::ReadChunkImpl()Hello!
I'm running a GUI QT application and use openvds+.
When I try to request some data from VDS, it throws an unhandled exception.
I was able to receive a stack of it and check for the reason linking against openvds built from sour...Hello!
I'm running a GUI QT application and use openvds+.
When I try to request some data from VDS, it throws an unhandled exception.
I was able to receive a stack of it and check for the reason linking against openvds built from sources.
The stack is as follows:
[External Code]
openvdsd.dll!fmt::v7::detail::do_throw(const fmt::v7::system_error & x) Line 108 C++
openvdsd.dll!fmt::v7::detail::fwrite_fully(const void * ptr, unsigned __int64 size, unsigned __int64 count, _iobuf * stream) Line 166 C++
openvdsd.dll!fmt::v7::detail::vprint_mojibake(_iobuf * f, fmt::v7::basic_string_view format_str, fmt::v7::format_args args) Line 2791 C++
openvdsd.dll!fmt::v7::print(_iobuf * f, const char[92] & format_str) Line 2096 C++
openvdsd.dll!OpenVDS::VolumeDataStoreIOManager::ReadChunkImpl(const OpenVDS::VolumeDataChunk & chunk, int adaptiveLevel, std::vector> & serializedData, std::vector> & metadata, OpenVDS::CompressionInfo & compressionInfo, OpenVDS::Error & error) Line 503 C++
openvdsd.dll!OpenVDS::VolumeDataStore::ReadChunk(const OpenVDS::VolumeDataChunk & chunk, int adaptiveLevel, std::vector> & serializedData, std::vector> & metadata, OpenVDS::CompressionInfo & compressionInfo, OpenVDS::Error & error) Line 306 C++
openvdsd.dll!OpenVDS::VolumeDataPageAccessorImpl::ReadPreparedPaged(OpenVDS::VolumeDataPage * page) Line 362 C++
openvdsd.dll!OpenVDS::ProcessPageInJob(OpenVDS::Job * job, int pageIndex, OpenVDS::VolumeDataPageAccessorImpl * pageAccessor, std::function processor) Line 2425 C++
openvdsd.dll!OpenVDS::VolumeDataRequestProcessor::AddJob::__l32::() Line 2562 C++
[External Code]
openvdsd.dll!ThreadPool::Enqueue::__l3::() Line 98 C++
[External Code]
openvdsd.dll!ThreadPool::{ctor}::__l3::() Line 72 C++
[External Code]
The reason is in the following code:
bool VolumeDataStoreIOManager::ReadChunkImpl(const VolumeDataChunk &chunk, int adaptiveLevel, std::vector &serializedData, std::vector &metadata, CompressionInfo &compressionInfo, Error &error)
{
...
fmt::print(stderr, "Dataset has missing metadata tags, degraded data verification, reverting to metadata pages\n");
Execution of `fmt::print` ends up with a method `fmt::v7::detail::fwrite_fully`:
// A wrapper around fwrite that throws on error.
inline void fwrite_fully(const void* ptr, size_t size, size_t count,
FILE* stream) {
size_t written = std::fwrite(ptr, size, count, stream);
if (written < count) FMT_THROW(system_error(errno, "cannot write to file"));
}
and here we can't write into stream (`stderr`) from GUI app and receive `written==0` and then this code throws 'system_error' exception which no one handles.
That is an important warning surely, but I suppose it shouldn't lead to unhandled exceptions.
I have seen the possibility to disable warnings with environment variables:
m_warnedAboutMissingMetadataTag(getBooleanEnvironmentVariable("OPENVDS_DISABLE_WARNINGS"))
but it can't be done programmatically on WIN since the environment is fixed by OS on process start and the application can not change its own environment.
I would suggest not using `fmt::print` to print into `stderr` and `using fmt::format` and `fprint(stderr)` instead.
PS: On the same VDS dataset, console utils like slicedump work OK (as expected, though printing warning message).https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/301GCP Search service throwing "elasticsearch.host not configured correctly for ...2022-06-06T09:36:25ZRakesh SharmaGCP Search service throwing "elasticsearch.host not configured correctly for partition odesprod"Hi,
we are using https://preship.gcp.gnrg-osdu.projects.epam.com/api/search/v2/query search endpoint but getting following error
```
Internal Server Error {"code":500,"reason":"Vital property not present in the environment","message":"...Hi,
we are using https://preship.gcp.gnrg-osdu.projects.epam.com/api/search/v2/query search endpoint but getting following error
```
Internal Server Error {"code":500,"reason":"Vital property not present in the environment","message":"elasticsearch.host not configured correctly for partition odesprod"}
```
Is there change in some configuration which needs to be done on our side?Dzmitry Malkevich (EPAM)Dzmitry Malkevich (EPAM)https://community.opengroup.org/osdu/platform/system/search-service/-/issues/93429 Elastic exception handling2022-07-22T13:24:43ZLarissa Pereira429 Elastic exception handling**Summary**: Due to a large number of requests from domain teams, Elastic search throws 429- Too many requests error whereas search service throws 5XX alerts bringing down the service availability. Therefore, we need to return 429 from S...**Summary**: Due to a large number of requests from domain teams, Elastic search throws 429- Too many requests error whereas search service throws 5XX alerts bringing down the service availability. Therefore, we need to return 429 from Search instead of 500 when ECK returns 429.https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/open-vds/-/issues/121For GCP OSDU environments the name of the DAG that performs the conversion fr...2022-06-13T20:13:48ZKamlesh TodaiFor GCP OSDU environments the name of the DAG that performs the conversion from SEGY to OpenVDS are not consistent.In the Platform Validation (GCP Dev2) environment the name of the DAG is "Segy_to_vds_conversion_sdms" and in the pre-ship environment name of DAG is "openvds_import"
Also, the document that describes how to trigger the workflow needs up...In the Platform Validation (GCP Dev2) environment the name of the DAG is "Segy_to_vds_conversion_sdms" and in the pre-ship environment name of DAG is "openvds_import"
Also, the document that describes how to trigger the workflow needs updating.
At present it says to trigger
```
curl --location --request POST 'https://<base_url>/api/workflow/v1/workflow/openvds_import/workflowRun' \
--header 'Content-Type: application/json' \
--header 'data-partition-id: opendes' \
--header 'Authorization: <Bearer Token>' \
--data-raw '{
"executionContext": {
"url_connection":"Region=us-east-1;AccessKeyId=XXX;SecretKey=XXX;SessionToken=XXX",
"input_connection":"Region=us-east-1;AccessKeyId=XXX;SecretKey=XXX;SessionToken=XXX",
"segy_file":"s3://aws-osdu-sample-data/sample-data/seismic/st0202/stacks/ST0202R08_PS_PSDM_RAW_PP_TIME.MIG_RAW.POST_STACK.3D.JS-017534.segy",
"url":"s3://aws-osdu-sample-data/"
}
}
But know if we one is going to create a File record as well as bingrid, seimictrace and work-product-component records then
url_connection and input_connection do not make sense?M12 - Release 0.15Yan Sushchynski (EPAM)Dzmitry Malkevich (EPAM)Yan Sushchynski (EPAM)https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/seismic/seismic-dms-suite/seismic-store-service/-/issues/61In GCP Platform Validation environment, cannot create subproject using Seismi...2022-06-07T07:00:33ZKamlesh TodaiIn GCP Platform Validation environment, cannot create subproject using Seismic DDMS APIs or using sdutilWhen I use sdutil, I get the following message
(sdutilenv) D:\OSDU\dev\seismic-store-sdutil-master>python sdutil mk "sd://autotesttenant/autotest" "admin@devtwo.osdu-gcp.go3-nrg.projects.epam.com" "devtwo-SeismicDMS-Legal-Tag-Test6345011...When I use sdutil, I get the following message
(sdutilenv) D:\OSDU\dev\seismic-store-sdutil-master>python sdutil mk "sd://autotesttenant/autotest" "admin@devtwo.osdu-gcp.go3-nrg.projects.epam.com" "devtwo-SeismicDMS-Legal-Tag-Test6345011" --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 autotest(tenant=autotesttenant) with admin@devtwo.osdu-gcp.go3-nrg.projects.epam.com as admin ...
[404] [seismic-store-service] 404 - "<!DOCTYPE html>\n<html lang=en>\n <meta charset=utf-8>\n <meta name=viewport content=\"initial-scale=1, minimum-scale=1, width=device-width\">\n <title>Error 404 (Not Found)!!1</title>\n <style>\n *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}\n </style>\n <a href=//www.google.com/><span id=logo aria-label=Google></span></a>\n <p><b>404.</b> <ins>That’s an error.</ins>\n <p>The requested URL <code>/v1/projects/</code> was not found on this server. <ins>That’s all we know.</ins>\n"
And when I use the Seismic DDMS API I get the following:
Request:
curl --location --request POST 'https://dev2.gcp.gnrg-osdu.projects.epam.com/api/seismic-store/v3/subproject/tenant/autotesttenant/subproject/autotest' \
--header 'Content-Type: application/json' \
--header 'data-partition-id: devtwo' \
--header 'ltag: devtwo-SeismicDMS-Legal-Tag-Test6345011' \
--header 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IjM4ZjM4ODM0NjhmYzY1OWFiYjQ0NzVmMzYzMTNkMjI1ODVjMmQ3Y2EiLCJ0eXAiOiJKV1QifQ.eyJpc3MiOiJodHRwczovL2FjY291bnRzLmdvb2dsZS5jb20iLCJhenAiOiI5MTA1MzI3MzI3MDAtZHI2OHU1MGFqNTMzbTdwb3E3YTBjajQwNG4zMHNwczAuYXBwcy5nb29nbGV1c2VyY29udGVudC5jb20iLCJhdWQiOiI5MTA1MzI3MzI3MDAtZHI2OHU1MGFqNTMzbTdwb3E3YTBjajQwNG4zMHNwczAuYXBwcy5nb29nbGV1c2VyY29udGVudC5jb20iLCJzdWIiOiIxMTAzNjA5OTgzOTQ5MjkwOTU3NjkiLCJoZCI6Im9zZHUtZ2NwLmdvMy1ucmcucHJvamVjdHMuZXBhbS5jb20iLCJlbWFpbCI6ImthbWxlc2hfdG9kYWlAb3NkdS1nY3AuZ28zLW5yZy5wcm9qZWN0cy5lcGFtLmNvbSIsImVtYWlsX3ZlcmlmaWVkIjp0cnVlLCJhdF9oYXNoIjoiSjNVaTRVYjcyMHZPSzBqMi1RZlZmdyIsImlhdCI6MTY1NDE5NDY4NywiZXhwIjoxNjU0MTk4Mjg3fQ.cAB3vLN88IzMWqcGAuxoBcqE2tobU0mfJkS8VVJ-gS-IoDzl7y7NDY48jOObJ5bfU2yROP5v2BhO_xT89mR_Ijqspp-UiqA5f1CGJQXkSAqPchd4NlOMzEe8RxgjtusC1w-hLoF-dzUMONxD4h7ZOJ2Niq6Oc8GVwMsAWsumuO7HyRb-_Eb1pZdg5Jb7D2_tOl6Vun7JjHSETJdUvDtpN5bRymuU2yj-vendv76h59ey3L--MObk-OktIXhg9o3cC0CCepe80ejU8Jgu5hmgUvZ2a0qewfgrrAvg_72vaaOr-BlEUv1czPAzCFuHJfbCgUOZKtQKVxKMW_s44x0XDA' \
--data-raw '{
"admin": "admin@devtwo.dev2.osdu.club",
"storage_class": "MULTI_REGIONAL",
"storage_location": "US",
"acls": {
"admins": [
"data.sdms.autotesttenant.autotest.admin@devtwo.dev2.osdu.club"
],
"viewers": [
"data.sdms.autotesttenant.autotest.viewer@devtwo.dev2.osdu.club"
]
},
"legal": {
"legaltags": [
"devtwo-SeismicDMS-Legal-Tag-Test6345011"
],
"otherRelevantDataCountries": [
"US"
]
}
}'
Response:
[seismic-store-service] 404 - "<!DOCTYPE html>\n<html lang=en>\n <meta charset=utf-8>\n <meta name=viewport
content=\"initial-scale=1, minimum-scale=1, width=device-width\">\n <title>Error 404 (Not Found)!!1</title>\n
<style>\n *{margin:0;padding:0}html,code{font:15px/22px
arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto
0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png)
100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a
img{border:0}@media screen and
(max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png)
no-repeat;margin-left:-5px}@media only screen and
(min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}\n </style>\n <a href=//www.google.com/><span id=logo aria-label=Google></span></a>\n <p><b>404.</b> <ins>That’s an error.</ins>\n <p>The requested URL <code>/v1/projects/</code> was not found on this server. <ins>That’s all we know.</ins>\n"M12 - Release 0.15Dzmitry Malkevich (EPAM)Dzmitry Malkevich (EPAM)https://community.opengroup.org/osdu/platform/consumption/geospatial/-/issues/132Testing - Execute user workflows to comprehensively test the service2022-08-03T15:19:15ZJoel RomeroTesting - Execute user workflows to comprehensively test the serviceAs a GIS Developer, I want to go through user workflows to comprehensively test the system, so that we can identify any issues or gaps.
- identify and document common workflows - will help with documentation that we will be providing to...As a GIS Developer, I want to go through user workflows to comprehensively test the system, so that we can identify any issues or gaps.
- identify and document common workflows - will help with documentation that we will be providing to the Testing team
- identify use cases to cover all functionality
- go through user workflows
**Acceptance Criteria **
- Defects or gaps are documented and triaged
- Common workflows are identified and documentedLevi RemingtonAnkita SrivastavaLevi Remington