Terraform state backend works unreliable on GitLab-EE deployed using the operator (status code 422)

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

The Terraform state backend seems to work unreliable when GitLab EE is deployed using the Kubernetes operator.

On destroy, a 422 status code is returned.

The only errors I can find in the logs are related to duplicate keys in Postgres:

I tested the same Terraform project with a regular Omnibus deployment and using the operator. The Omnibus instance works fine.

• GitLab 15.2.0-ee
• GitLab Shell14.9.0
• GitLab Workhorsev15.2.0
• GitLab APIv4
• GitLab KAS15.2.0
• Ruby 2.7.5p203
• Rails 6.1.4.7
• Postgre SQL12.7
• Redis 6.0.9