Jenkins Cloud Agent Provisioning Failed

A cloud plugin could not provision a dynamic agent for the build, so the job stayed queued or failed to start.

What this error means

The build waits for an executor while the cloud plugin logs a provisioning error, or the build fails because no agent could be created in time.

jenkins

ERROR: Unable to provision agent for label 'k8s-build'
io.fabric8.kubernetes.client.KubernetesClientException: Pod failed to schedule: Insufficient cpu

Common causes

Cluster or quota exhaustion

No node capacity or a cloud quota cap prevents creating the agent.

Misconfigured pod/template or credentials

A bad image, resource request, or expired cloud credential blocks provisioning.

Cloud API throttling or outage

The provider throttled or briefly failed agent creation.

How to fix it

Check capacity and quotas

Inspect cluster node capacity and cloud quotas for the agent type.
Reduce resource requests or add capacity.

Terminal

kubectl describe pod -l jenkins=agent | grep -A3 Events

Validate the agent template

Confirm the image, resource requests, and cloud credentials are valid.

How to prevent it

If you run on GitHub Actions, self-healing managed runners such as Latchkey auto-retry transient failures and re-provision runners, so a one-off provisioning failure does not fail the job. On Jenkins, keep cloud quotas and templates healthy.