Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IAM] Secuity Settings API Error on create #2507

Closed
dampsoft-david opened this issue May 17, 2024 · 3 comments
Closed

[IAM] Secuity Settings API Error on create #2507

dampsoft-david opened this issue May 17, 2024 · 3 comments
Assignees
Labels

Comments

@dampsoft-david
Copy link

dampsoft-david commented May 17, 2024

Terraform provider version

tf providers -v
Terraform v1.8.3
+ provider registry.terraform.io/opentelekomcloud/opentelekomcloud v1.36.8

Affected Resource(s)

  • opentelekomcloud_identity_login_policy_v3
  • opentelekomcloud_identity_password_policy_v3
  • opentelekomcloud_identity_protection_policy_v3

Terraform Configuration Files

terraform {
  required_providers {
    opentelekomcloud = {
      source  = "opentelekomcloud/opentelekomcloud"
      version = "~> 1"
    }
  }
}

provider "opentelekomcloud" {
  access_key  = ""
  secret_key  = ""
  domain_name = ""
  tenant_name = "eu-de"
  region      = "eu-de"
  auth_url    = "https://iam.eu-de.otc.t-systems.com/v3"
}

resource "opentelekomcloud_identity_protection_policy_v3" "this" {
  enable_operation_protection_policy = true
}

Debug Output/Panic Output

opentelekomcloud_identity_protection_policy_v3.this: Creating...
Error: error updating the IAM operation protection policy: Resource not found: [PUT https://iam.eu-de.otc.t-systems.com/v3.0/OS-SECURITYPOLICY/domains//protect-policy], error message: {"error_msg":"The API does not exist or has not been published in the environment","error_code":"APIGW.0101","request_id":"71d53ba40c3ad62cdea44b5e9ce5996b"}

Steps to Reproduce

  1. terraform init
  2. terraform apply

Expected Behavior

Setting the desired option values

Actual Behavior

Error

Important Factoids

Hi,

we encountered a Problem with using the IAM Security Setting Resources as shown down above. (example only show one resource but all 3 are affected)
If we import the resources before applying everything works as expected, so it seems there is something wrong with the initial creation/importing.

@artem-lifshits artem-lifshits self-assigned this May 17, 2024
@artem-lifshits
Copy link
Member

Hello @dampsoft-david I was able to reproduce the issue, it will be fixed on next release.
Until that as a workaround user/password auth can be used.

otc-zuul bot pushed a commit that referenced this issue May 17, 2024
[IAM]: fix ak/sk auth

Summary of the Pull Request
PR Checklist

 Refers to: #2507
 Tests passed.
 Release notes added.

Acceptance Steps Performed
=== RUN   TestAccIdentityV3Login_basic
--- PASS: TestAccIdentityV3Login_basic (45.68s)
PASS

Process finished with the exit code 0

=== RUN   TestAccIdentityV3Password_basic
--- PASS: TestAccIdentityV3Password_basic (46.36s)
PASS

Process finished with the exit code 0

2024/05/17 16:26:58 [INFO] Building Swift S3 auth structure
2024/05/17 16:26:58 [INFO] Setting AWS metadata API timeout to 100ms
2024/05/17 16:27:00 [INFO] Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id
2024/05/17 16:27:00 [INFO] Swift S3 Auth provider used: "StaticProvider"
=== RUN   TestAccIdentityV3Protection_basic
--- PASS: TestAccIdentityV3Protection_basic (148.35s)
PASS

Process finished with the exit code 0

Reviewed-by: Anton Sidelnikov
@artem-lifshits
Copy link
Member

@dampsoft-david fixed in latest release, please check.

@dampsoft-david
Copy link
Author

@artem-lifshits thanks for the quick fix. Works for me now with v1.36.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants