Azure/ACS

ACS - Unable to change VM count

ankitpopli1891 opened this issue · 5 comments

ankitpopli1891 commented

Is this a request for help?:
Yes

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
Bug

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes

Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.7", GitCommit:"8e1552342355496b62754e61ad5f802a0f3f1fa7", GitTreeState:"clean", BuildDate:"2017-09-28T23:56:03Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.7", GitCommit:"8e1552342355496b62754e61ad5f802a0f3f1fa7", GitTreeState:"clean", BuildDate:"2017-09-28T23:56:03Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

What happened:

Command

az acs scale -n xxxxx-acs --new-agent-count 2 -g xxxxx

Deployment failed. Correlation ID: xxxxx. Provisioning of resource(s) for container service 'xxxxx-acs' in resource group 'xxxxxx' failed with errors: Resource type: Microsoft.Network/publicIPAddresses, name: k8s-master-ip-xxxxxx, id: /subscriptions/xxxxxxx/resourceGroups/xxxxxx/providers/Microsoft.Network/publicIPAddresses/k8s-master-ip-xxxxx, StatusCode: BadRequest, StatusMessage: \n {
  "error": {
    "code": "PublicIPAddressInUseCannotUpdateToDynamic",
    "message": "Public IP address /subscriptions/xxxxx/resourceGroups/xxxxx/providers/Microsoft.Network/publicIPAddresses/k8s-master-ip-xxxxx is in use by ipconfig /subscriptions/xxxxx/resourceGroups/veris-vms/providers/Microsoft.Network/loadBalancers/k8s-master-lb-xxxxxx/frontendIPConfigurations/k8s-master-lbFrontEnd-xxxxx and cannot be updated from static to dynamic.",
    "details": []
  }
}

What you expected to happen:
The agent count should change to 2.

How to reproduce it (as minimally and precisely as possible):
Follow the docs on Scale agent nodes in a Container Service cluster

  • Either by Azure Dashboard or by Azure CLI

Anything else we need to know:

foram31k commented

@ankitpopli1891 Is your Load Balancer IP / master VM's IP static ?

ankitpopli1891 commented

@foram31k Yes.

Did try to make it dynamic, wasn't successful. Can't remember the issues faced, tried it more than a month earlier. Finally, decided to raise an issue.

foram31k commented

@ankitpopli1891
I had faced the same issue, by following these steps my issue was resolved.

STEPS TO MITIGATE THE ISSUE

  1. Login to Portal.
  2. Navigate to Load Balancer k8s-master-lb
  3. Create a new Public IP address (Dynamic) and associate with the Load Balancer.
  4. Save the Settings.
  5. Once the settings are saved, verify that the Load Balancer is associated with newly created Public IP address.
  6. Increase the Agent Pool Count.
  7. Once the agent Pool count is increased successfully navigate to the load balancer and change the dynamic public IP associated with the LB to the previous static public IP address.
  8. Save the changes.
ankitpopli1891 commented

@foram31k Thanks for the solution. It did help me move forward, now I get a different error.

{ "error": { "code": "RulesUseSameFrontendPortAndProtocol" } }

I'll try a few different things, & reach back if it doesn't work.

ankitpopli1891 commented

The weird thing is I'm being billed for 2 agents and the count is still 1.
image

& actually there are 2 agents running.
image