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

azurerm_kubernetes_cluster gridlocks future terraform apply due to it deciding to also change service_principal #6257

Closed
tezzigator opened this issue Mar 25, 2020 · 2 comments · Fixed by #6095

Comments

@tezzigator
Copy link

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 "me too" comments, 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 (and AzureRM Provider) Version

TF 0.12.23, azure 2.2.0

Affected Resource(s)

azurerm_kubernetes_cluster

Terraform Configuration Files

  service_principal {
    client_id     = var.clientid
    client_secret = var.clientsecret
  }

Debug Output

the cluster's initial deployment works, but then a future plan results in:
~ service_principal {
~ client_id = "msi" -> "<REDACTED-SP-CLIENTID_UUID>"
client_secret = (sensitive value)
}
and then the apply errors with:
Error: Error updating Service Principal for Kubernetes Cluster "K8Scluster" (Resource Group "lab1"): containerservice.ManagedClustersClient#ResetServicePrincipalProfile: Failure sending request: StatusCode=400 -- Original Error: Code="BadRequest" Message="Updating service principal profile is not allowed on MSI cluster."

on modules\k8s\main.tf line 23, in resource "azurerm_kubernetes_cluster" "k8s":
23: resource "azurerm_kubernetes_cluster" "k8s" {

Expected Behavior

resource should be unchanged

@ghost
Copy link

ghost commented Apr 9, 2020

This has been released in version 2.5.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.5.0"
}
# ... other configuration ...

@ghost
Copy link

ghost commented May 6, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators May 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants