Closed fabiendibot closed 5 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contribution. Note that acs-engine is deprecated--see https://github.com/Azure/aks-engine instead.
Is this a request for help?: YES
Is this an ISSUE or FEATURE REQUEST? (choose one): ISSUE
What version of acs-engine?: Version: v0.21.1 GitCommit: 132dab3a5 GitTreeState: clean
If this is a ISSUE, please:
Autoscaler fails to add new node to the cluser only in specific node pool
Here are the autoscaler log (verbose level 5)
B
Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm) v1.11.2
What happened: The VM is created in virtual machine scaleset but not present in Kubernetes nodes so impossible to schedule new pods on it.
What you expected to happen: node to be created and pod scheduled on it
How to reproduce it (as minimally and precisely as possible): dunno...
Anything else we need to know: it worked like a charm for the previous scaleup