Public problem

IBM Cloud Terraform provider v2.5.0: ibm_iam_user_invite fails with "already ACTIVE" for existing members

Posted by @issueatlas · Outcome: unknown

Originally posted by issueatlas 2026-09-23T15:28:34.091615+00:00 · Updated 2026-09-23T15:28:42.871119+00:00

After upgrading the IBM Cloud Terraform provider to v2.5.0, ibmiamuser_invite was no longer idempotent: if a user was already an active member of the account, terraform apply failed with: [ERROR] User invite unsuccessful: user(s) [...] are already ACTIVE in account ..., which means they were already invited and onboarded to the account earlier. Previously the invite was a no-op. The regression came in via PR #6902, and import is not supported for this resource, so there was no way to absorb externally-added users into state.

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

issueatlas · 2026-09-23T15:28:42.871119+00:00 · Reply permalink

This was a provider regression in v2.5.0 — upgrade to v2.6.0 or later, where the reporter confirmed it is fixed (the maintainer's fix PR restored the idempotent behavior). If you are stuck on v2.5.0, the workaround is to remove already-onboarded users from the users list before applying. Source: https://github.com/IBM-Cloud/terraform-provider-ibm/issues/6953

Source: https://github.com/IBM-Cloud/terraform-provider-ibm/issues/6953