-
Notifications
You must be signed in to change notification settings - Fork 27
Unable to change agents count in ACS #14
Comments
Thanks for reporting this. We have identified the issue. We are making a plan for how to roll out this fix globaly and should have an ETA for you shortly. After the fix your existing clusters will work properly in the portal. There needs to also be a fix to the Azure CLI 2.0 to not verify the password is non null. |
When trying to validate changes in the CLI I ran into another issue. So ETA for ETA is now delayed |
Circling back. I've been working on getting this unblocked. I've encountered a number of issues with the windows code paths. Still don't have a firm ETA on the world wide deployment but we are getting much closer. |
I've peeled the onion far enough that I got this working. We are currently rolling out a fix. The rollout should be finished by 4/14 at the latest. When that happens I will also push for this update in the az cli to get az scale working for windows clusters. |
The fix is now globally rolled out and this should no longer be an issue in the portal. I authored a PR on the cli to enable changing windows clusters and they merged it but it hasn't been tagged for a release yet. |
@JackQuincy when the fix will be available for Azure CLI and would the following command |
Thought I had answered this. Yes that command was enough for me. This works today so I'm going to close this |
* added support for custom vnet for DCOS * added VNET templates for dockerce and kubernetes
I have deployed a wind + k8s cluster on azure container service and then I tried to change the agentpool from 1 to 2 agents and got the error.
![screenshot 2017-03-16 10 38 57](https://cloud.githubusercontent.com/assets/9897945/23983362/640fde76-0a35-11e7-93b1-75052b8ddc3f.png)
I have also tried scaling using Azure CLI 2.0 and getting this error:
Parameter 'ContainerServiceWindowsProfile.admin_password' can not be None.
I have used this cmd:
az acs scale -g acs-test-d3 -n containerservice-acs-test-d3 --new-agent-count 3
The text was updated successfully, but these errors were encountered: