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

Terraform error : Provider produced inconsistent result after apply #12105

Closed
rajatb2 opened this issue Jun 8, 2021 · 5 comments
Closed

Terraform error : Provider produced inconsistent result after apply #12105

rajatb2 opened this issue Jun 8, 2021 · 5 comments

Comments

@rajatb2
Copy link

rajatb2 commented Jun 8, 2021

image
I am getting this issue on terraform. I am also getting role assignment already exists issue.
image
when i run terraform apply it creates resources and and show unknown role assignments and on re-run it show resource exist error,
i am using count function on my aks module , can this be the cause of error.

@aristosvo
Copy link
Collaborator

@rajatb2 Thanks for submitting!

I believe this is a duplicate of #12057 and #12060, the solution is in the works and hopefully ready for the release of this week.

Until then, the best solution is to roll back to 2.61, remove your role assignments manually in the Portal and recreate them.

Another option is to define the scope on resource group instead of resource.

@rajatb2
Copy link
Author

rajatb2 commented Jun 8, 2021

@aristosvo while defining scope on resource group , again i am getting the same issue " Provider produced inconsistent result after apply ", I deleted all the role assignments manually and then try to recreate them but it seems like some of them get created and some named as unknown. And again am getting this issue
image

@aristosvo
Copy link
Collaborator

@rajatb2 Can you retry it with 2.62.1? This should've fixed the problems we had with azurerm_role_assignment

@rajatb2
Copy link
Author

rajatb2 commented Jun 9, 2021

@aristosvo thansk , this issue has been resolved . closing this issue

@rajatb2 rajatb2 closed this as completed Jun 9, 2021
@github-actions
Copy link

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 10, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants