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
News from Microsoft
Hello Olivier;
Greetings from Microsoft.
Thank you for your time on the call.
Please note that the current case update is as follows: The engineering team has identified the cause of the issue to be related to storage accounts where the vhds for the VM’s are hosted, the storage account in inaccessible and to fix the issue we will be deploying a hotfix from the backend.
As these steps do involve a lot of RND and testing so we should be able to roll out the hotfix expected time frame is by Friday.
We will keep you posted on the development as and when they appear.
We thank you once again for your valuable patience and cooperation.
Please do email me in case if you need any further help on the case.
I provided to the azure support, a list of virtual machines that need to be deleted.
But of course this won't prevent the issue to appear again in the futur if the root cause is not identify.
I also opened a ticket for the plugin JENKINS-52317
I was able to delete all failed VM, and I cleaned up the node list on ci.jenkins.io