Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: azure, ci.jenkins.io
-
Labels:None
-
Similar Issues:
Description
ci.jenkins.io doesn't provision agents anymore
This seems to be caused by the fact that sometimes agent aren't correctly deleted and are stuck in a 'failed' state.
Those 'failed' agents are taken into account in the limit of Jenkins agent vms (configured by the plugin).
This morning we had 65 broken agents which was the hard limit configured from Jenkins.
Remark: We also have 'broken' agents in trusted.ci
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Description |
ci.jenkins.io doesn't provision agents anymore This seems to be caused by the fact that *sometimes* agent aren't correctly deleted and are stuck in a 'failed' state. Those 'failed' agents are taken into account in the limit of Jenkins agent vms (configured by the plugin). This morning we had 65 broken agents which was the hard limit configured from Jenkins. Remark: We also have 'broken' agent in trusted.ci |
ci.jenkins.io doesn't provision agents anymore This seems to be caused by the fact that *sometimes* agent aren't correctly deleted and are stuck in a 'failed' state. Those 'failed' agents are taken into account in the limit of Jenkins agent vms (configured by the plugin). This morning we had 65 broken agents which was the hard limit configured from Jenkins. Remark: We also have 'broken' agents in trusted.ci |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |