-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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 can not use Count attribute correctly #6516
Comments
Hi @clintonm9 Just a FYI, I am looking at this issue right now Paul |
Hi @clintonm9 So I have been speaking to @jen20 about this issue. He has said that it is fixed in master. I will see if he can comment here with some answers on how it was fixed :) Paul |
Using Terraform master, I was able to create everything with a count of 2
When i increase the count to 3, the plan looks as follows:
the apply throws the error:
So looks like this is still not fixed. Will follow up with @jen20 again |
OK this looks like a different problem to the one I was expecting. We will investigate. |
@clintonm9 Do you still see this error? Everything seems to be working fine for me. I was able to change count from 1 to 2 to 1 without problems. Thx. |
It looks like now when I run an apply and then a plan afterward, it does not try and change the current vms. Once I change the count from 3 to 4 I get the following change (this is brief):
It looks like when I ran the apply that it seem liked it worked. I didnt check if the other VMs that were already up were reset or not. |
Hi @clintonm9 Thanks for bearing with us here. I've run the configuration posted above, including scaling the machine count up and down - and I can confirm @StephenWeatherford's comments in that this issue appears to be resolved. As such I'm going to close this issue for the moment - but please feel free to re-open it if there's still an issue here :) Thanks! |
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. |
When using the asurerm provider and a count attribute, I can get the initial vm's up and running. When I adjust the count up it tries and change some of the already running vm's.
Config:
https://gist.github.com/clintonm9/b568686fc25456250d5a206e4017e26a
Changing the count from 2 to 3 then running a plan:
If I try and apply I get the following error:
https://gist.github.com/clintonm9/c222763a91be6aca7be57478b9f8e8a0
The text was updated successfully, but these errors were encountered: