-
Notifications
You must be signed in to change notification settings - Fork 27
Unable to re-deploy when agent pool uses managed disks #62
Comments
@sjdweb thanks for reporting. we are tracking this. |
@sjdweb wondering how do you do the deployment? Can you give detail steps? When you say, you will need to |
I tried using az cli to re-deploy right after the initial deployment succeed. It doesn't throw any error. I guess, there is some change in your Note, we don't support any update scenario except for scaling. For managed disks agents, apparently, we don't support any kind update for now. |
On a side note ACS-Engine now supports scaling down with managed disks so we can just remove our check and start supporting it as well. |
@JackQuincy , how about scaling up with managed disks? |
@rjtsdl Hi, thanks for getting back. I can consistently reproduce the error by redeploying the ARM template with no changes, straight after an initial deployment. Has there been an update recently? I am running
Yes, to the Service Bus section of resources - this is the reason behind needing to redeploy, but I see the error even without any change to the ARM file. |
@sjdweb , as @JackQuincy pointed out, we are going to remove the scaling gate for managedDisks agent with k8s. I will update this thread later. |
hi @rjtsdl was this resolved? seems to be working (on a new cluster) as of today. |
yes it is. Closing the issue. |
Is this a request for help?:
Yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug
We're using managed disks mainly for the disk encryption that comes for free and requires no key management.
The deployment template has various other things in them, and we tend to redeploy often - we may add a new subscription to a Azure Service Bus topic for example.
We're not even trying to scale the cluster in any way.
Currently this bug will block the deployment.
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes
What happened:
What you expected to happen:
If we're not trying to scale the agent pool (as the error says) - the deployment should pass.
How to reproduce it (as minimally and precisely as possible):
Deploy a new azure cluster service with managed disks for your agent pool. Immediately re-deploy, you'll see the error.
Anything else we need to know:
No.
The text was updated successfully, but these errors were encountered: