opentelekomcloud_evs_volume_v3 cant be used with opentelekomcloud_kms_key_v1

[v1nc3nt27]

Terraform provider version

Affected Resource(s)

opentelekomcloud_evs_volume_v3
opentelekomcloud_kms_key_v1

Terraform Configuration Files

resource "opentelekomcloud_kms_key_v1" "kms" {
  key_alias       = "test"
  pending_days    = "7"
  key_description = "KMS for test"
  is_enabled      = true
  realm = "eu-de-01"
}

resource "opentelekomcloud_evs_volume_v3" "evs" {
  name              = "test"
  description       = "Data volume for test"
  availability_zone = "eu-de-01"
  volume_type       = "SATA"
  size              = "20"
  kms_id            = opentelekomcloud_kms_key_v1.kms.id
  multiattach       = true
}

Debug Output/Panic Output

Steps to Reproduce

1. terraform apply

Expected Behavior

The EVS should be created

Actual Behavior

╷
│ Error: error creating OpenTelekomCloud EVS volume: Resource not found: [POST https://evs.eu-de.otc.t-systems.com/v3/9f664c9b1d3d478c9b3f3257b4db5df8/cloudvolumes], error message: {"error":{"message":"get Agency's token but response is null.","code":"EVS.2265"}}
│
│ with opentelekomcloud_evs_volume_v3.evs[0],
│ on main.tf line 121, in resource "opentelekomcloud_evs_volume_v3" "evs":
│ 121: resource "opentelekomcloud_evs_volume_v3" "evs" {

If i remove the kms id, the EVS is created. What i noticed is that, even if i set the realm to "eu-de-01" as the doc suggests, it gets reverted to eu-de. I am new to OTC but from what i understand is that KMS is AZ-independent. Hence, there may be problems to find the KMS when the EVS is deployed?

We need multiattach and encryption, so this seems to be the only option we have. Has anyone else encountered this issue?