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

Error: Can not assign IaaS for non-linked account #1114

Closed
soliverprofesional opened this issue Feb 19, 2020 · 3 comments
Closed

Error: Can not assign IaaS for non-linked account #1114

soliverprofesional opened this issue Feb 19, 2020 · 3 comments
Assignees

Comments

@soliverprofesional
Copy link

Hi there,

Terraform Version

Terraform v0.12.20

  • provider.ibm v1.2.1

Affected Resource(s)

  • ibm_iam_user_invite

Terraform Configuration Files

#--> Identify the providers
terraform {
  required_version = "v0.12.20"
  required_providers {
    ibm = "~> 1.2.1"
  }
}

provider "ibm" {}
variable "user1" {}

resource "ibm_iam_user_invite" "invite_user" {
    users = [var.user1]
}

Expected Behavior

Invite the user, as it does through the console or the IBM Cloud CLI

Actual Behavior

Fails with the error:

Error: Request failed with status code: 401, ServerErrorResponse: {"trace":"51719293124","errors":[{"code":1025,"message":"Not Authorized.","more_info":"Can not assign IaaS for non-linked account."}]}

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. terraform apply -auto-approve

Important Factoids

None

References

None I know about

@hkantare
Copy link
Collaborator

can you please try same user invite using ibmcloud cli. Terraform calls the respective user management API and returns back the repsonse

ibmcloud account user-invite XXXXX

IF you see same response may be you can open IBM support ticket

@soliverprofesional
Copy link
Author

As indicated in "Expected Behavior" section, the IBM Cloud CLI works as expected.

Anil-CM added a commit to Anil-CM/terraform-provider-ibm that referenced this issue Feb 25, 2020
hkantare pushed a commit that referenced this issue Feb 25, 2020
@hkantare
Copy link
Collaborator

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

No branches or pull requests

3 participants