<p>I am using manual scaling in an Azure AKS cluster, which can scale up to 60 nodes.</p>
<p>Scaling command worked fine:</p>
<pre><code>az aks scale --resource-group RG-1 --name KS-3 --node-count 46
{- Finished ..
  &quot;agentPoolProfiles&quot;: [
    {
      &quot;availabilityZones&quot;: null,
      &quot;count&quot;: 46,
      ...
</code></pre>
<p>and reported the count of 46 nodes.</p>
<p>The status also shows &quot;Succeeded&quot;:</p>
<pre><code>az aks show --name KS-3 --resource-group RG-1 -o table
Name        Location    ResourceGroup       KubernetesVersion    ProvisioningState    Fqdn
----------  ----------  ------------------  -------------------  -------------------  -------------------------
      KS-3  xxxxxxx     RG-1                1.16.13              Succeeded            xxx.azmk8s.io
</code></pre>
<p>However, when I look at <code>kubectl get nodes</code> it shows only 44 nodes:</p>
<pre><code>kubectl get nodes | grep -c 'aks'
44
</code></pre>
<p>with 7 nodes in &quot;Ready,SchedulingDisabled&quot; state (and the rest in Ready state):</p>
<pre><code>kubectl get nodes | grep -c &quot;Ready,SchedulingDisabled&quot;
7
</code></pre>
<p>When I try to scale the cluster down to 45 nodes, it gives this error:</p>
<pre><code>Deployment failed. Correlation ID: xxxx-xxx-xxx-x. Node 'aks-nodepool1-xxxx-vmss000yz8' failed to be drained with error: 'nodes &quot;aks-nodepool1-xxxx-vmss000yz8&quot; not found'
</code></pre>
<p>I am not sure what got the cluster into this inconsistent state and how to go about debugging this.</p>

<p>It happened because two of the nodes were in corrupted state. We had to delete these nodes from the VM scale set in the node resource group associated with our AKS cluster. Not sure why the nodes got into this state though.</p>
