Data Generator Import setting handling appears to sometime fail
With !513 (merged), we added the ability for GPT Data Generator to specifically set the target environment's import settings to allow for GitLab project tarballs to be imported.
However this sometimes appears to still fail randomly:
| Vertical data: importing large projects for GPT...
Group gpt already exists
Creating group gpt/large_projects
Checking if project gitlabhq1 already exists in gpt/large_projects/gitlabhq1...
Configuring Import Sources setting to allow for GitLab project imports...
Updating application settings: {:import_sources=>["gitlab_project"]}
[...]
Importing project gitlabhq1...
Start time: 09:34:41 2024-03-05 UTC
Uploading project tarball to the target environment Import API...
GPT data generation failed:
ImportProject::ProjectImportError - Project import request has failed with the following error:
Code: 403
Response: {"message":"403 Forbidden"}
Correlation ID: <redacted>
This is very likely to be an issue with the target environment. To troubleshoot please refer to https://gitlab.com/gitlab-org/quality/performance/-/blob/main/docs/environment_prep.md#import-has-failed
Restoring the original 'import_sources' setting...
Updating application settings: {:import_sources=>[""]}
Checking everything over it all still looks to be correct and setting the same variable manually continues to work.
As such, this may be a possible race condition where the setting is updated but it's not filtered through to the backend in time. Task is to investigate.