Repository navigation
stackit_valkey_instance: instance creation fails if instance name matches project name #1851
Description
Description
A stackit_valkey_instance that has its name set to the same value as the STACKIT project name fails at tofu apply with the following error Calling API: 400 Bad Request, Body: {"error":"Provision failed. service provision failed. The service instance name is taken: <name-same-as-project-name>-internal.","description":"""}
The tofu plan itself shows the planned instance name correctly as <name-same-as-project-name>.
Steps to reproduce
resource "stackit_valkey_instance" "this" {
project_id = "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
name = "same-name-as-project"
version = "8"
plan_name = "stackit-keyvalue-1.4.10-single"
}- Run
tofu apply
Actual behavior
The STACKIT API instantly fails the instance creation and is returning a 400 for the provisioning API call.
Error message:
| Error: Error creating instance
| with stackit_valkey_instance.this,
| on main.tf line 1, in resource "stackit_valkey_instance" "this":
| 1: resource "stackit_valkey_instance" "this" {
|
| Calling API: 400 Bad Request, Body: {"error":"Provision failed. service provision failed. The service instance name is taken: <name-same-as-project-name>-internal.","description":"""}Expected behavior
Either a stackit_valkey_instance can be created with the same name as the project (for consistency with other STACKIT service names where this is not a problem, like e.g. postgres, redis, secretsmanager) or there is a warning/error (possibly at plan already) that naming this instance the same as the project will not work.
Environment
- OS: Linux
- OpenTofu version (see
tofu --version):v1.13.1 - Version of the STACKIT Terraform provider:
v0.120.0
Activity
[-]stackit_valkey_instance: instance creation fails if instance names matches project name[/-][+]stackit_valkey_instance: instance creation fails if instance name matches project name[/+]Manuelvaas commentedon Oct 26, 2026
Hi @Gallowbraid,
thank you for reporting this issue. We will take a look at it.
Fyusel commentedon Oct 26, 2026
Hi @Gallowbraid,
I am trying to reproduce this behavior but I don't receive this issue. On my side it is possible to create a valkey instance with the same name as the project.
I only see this message when another valkey instance with the same name is present.
Gallowbraid commentedon Oct 28, 2026
Hi @Fyusel,
thanks for investigating!
I retried it via CLI (this throws the same error as tofu) and in the portal (this does not do anything, i can click the create button multiple times but nothing happens). This was done in EU01.
If i try to create an instance via the portal in EU02 like you, then it works and the instance can be created with the same name as the project.
There seems to be some mismatch between the regions.
Fyusel commentedon Oct 29, 2026
Hi @Gallowbraid,
I just rerun my test against EU01 but cannot see this issue on my side as well.
Can you please provide a trace id for this case then I can inform the corresponding service team to have a look at this.