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

Apply for iam_service_id fails with 404 when using IBMCLOUD_VISIBILITY=private #2560

Closed
l2fprod opened this issue Apr 29, 2021 · 8 comments · Fixed by #2720
Closed

Apply for iam_service_id fails with 404 when using IBMCLOUD_VISIBILITY=private #2560

l2fprod opened this issue Apr 29, 2021 · 8 comments · Fixed by #2720
Labels
bug service/IAM Issues related to IAM Visibility

Comments

@l2fprod
Copy link
Member

l2fprod commented Apr 29, 2021

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform IBM Provider Version

Affected Resource(s)

  • ibm_iam_service_id

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

terraform {
  required_providers {
    ibm = {
      source  = "IBM-Cloud/ibm"
      version = ">= 1.23.2"
    }
  }
}

provider "ibm" {
}

resource "ibm_iam_service_id" "functional_user" {
  name = "test-private-functional-user"
}

Expected Behavior

Apply should have worked

Actual Behavior

$ terraform apply -auto-approve
ibm_iam_service_id.functional_user: Creating...
╷
│ Error: Error creating serviceID: Request failed with status code: 404, ServerErrorResponse: <!DOCTYPE html><html><head><title>Error</title><style>body {
│         width: 35em;
│         margin: 0 auto;
│         font-family: Tahoma, Verdana, Arial, sans-serif;
│     }
│ </style></head><body><h1>An 404 error occurred in iam-gateway.</h1></body></html>
│
│   with ibm_iam_service_id.functional_user,
│   on main.tf line 13, in resource "ibm_iam_service_id" "functional_user":13: resource "ibm_iam_service_id" "functional_user" {
│
╵

Steps to Reproduce

export IBMCLOUD_VISIBILITY=private
terraform init
terraform apply

Things work if IBMCLOUD_VISIBILITY=public

@kavya498
Copy link
Collaborator

#2539

@l2fprod
Copy link
Member Author

l2fprod commented Apr 30, 2021

@kavya498 FYI I built the latest provider from master and tried to use it but it does not seem to fix the issue I'm seeing

@l2fprod
Copy link
Member Author

l2fprod commented May 4, 2021

@kavya498

just tested with latest provider and this still fails when VISIBILITY is private

$ terraform version
Terraform v0.15.1
on darwin_amd64
+ provider registry.terraform.io/ibm-cloud/ibm v1.24.0

I can see the provider calling private.us-south.iam.cloud.ibm.com when I do tcpdump

@kavya498
Copy link
Collaborator

kavya498 commented May 4, 2021

okay..
Is it working fine for your scenerio?

@l2fprod
Copy link
Member Author

l2fprod commented May 4, 2021

no it still fails

@l2fprod
Copy link
Member Author

l2fprod commented May 4, 2021

@kavya498

is there any way to show more debug traces like the API calls?

@kavya498 kavya498 added enhancement service/IAM Issues related to IAM labels May 6, 2021
@kavya498
Copy link
Collaborator

kavya498 commented May 6, 2021

SDK issue,
provider SDK has to be migrated to v1 APIs

@l2fprod
Copy link
Member Author

l2fprod commented Jun 3, 2021

@kavya498 when is this planned to be fixed? It should be marked as a BUG, not an enhancement. The feature is currently broken.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug service/IAM Issues related to IAM Visibility
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants