<p>I have two nodepools on GKE for CI runners, the workers nodepool is set to autoscale between 0-40 nodes. Up until yesterday this has been working perfectly for ~6months but now I am getting an inconsistent error around <code>nap</code> being disabled.</p>
<p>Pods scheduling fine this morning:</p>
<pre><code>decision: {
  decideTime: &quot;1616746520&quot; // Friday, 26 March 2021 08:15:20 GMT
  scaleUp: {
</code></pre>
<p>At some point they started failing because of <code>nap.disabled</code>:</p>
<pre><code>noDecisionStatus: {
  measureTime: &quot;1616756707&quot; // Friday, 26 March 2021 11:05:07 GMT
  napFailureReason: {
    messageId: &quot;no.scale.up.nap.disabled&quot;
  }
</code></pre>
<p>This is technically correct in that the cluster itself has node auto-provisioning disabled, but the nodepool <code>workers2</code> has auto scaling from 0-40 nodes.</p>
<p>I can't seem to find any information around why I would get this error when the nodepool itself should scale, nor can I see any reason why pods would suddenly not trigger the autoscaling of the nodepool.</p>
<p>Any ideas where I can dig to find more info or stop that error from blocking the autoscaling?</p>

Guy
<p>Creating a new node pool and destroying the old one seems to have fixed this, unfortunately no more insight than that</p>
