Kubernetes Agent Provisioning is stuck waiting on 'KubernetesCloud.provision'

Article ID:360054437112
1 minute readKnowledge base

Issue

  • Kubernetes Agent provisioning is slow / stuck causing the build queue to grow

  • Many threads are BLOCKED on org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision waiting on a lock on org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud:

"Computer.threadPoolForRemoting [#11599]" #350850 daemon prio=5 os_prio=0 tid=0x00007f5e581bf800 nid=0x4f9a waiting for monitor entry [0x00007f5da6db9000]
   java.lang.Thread.State: BLOCKED (on object monitor)
	at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:539)
	- waiting to lock <0x00000002f33e6f38> (a org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud)
	[...]

Environment

Related Issue(s)

Resolution

The lock contention problem has been fixed in version 1.28.3 of the kubernetes plugin.

The recommended solution is to upgrade CloudBees CI to version 2.263.1.2 that includes this version of the plugin.

Workaround

If a core upgrade is not an option in short term, the workaround is to upgrade the kubernetes plugin to a fixed version. The fix has been backported to different baselines of the plugin:

  • If using kubernetes plugin version 1.28.x, upgrade the kubernetes plugin to version 1.28.3

  • If using kubernetes plugin version 1.27.x, upgrade the kubernetes plugin to version 1.27.7

  • If using kubernetes plugin version 1.26.x, upgrade the kubernetes plugin to version 1.26.6

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.