You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What Operating System are you using (both controller, and any agents involved in the problem)?
Controller:
OS: Ubuntu 20.04.6 LTS
JDK: 21.0.5
Agents:
OS: Microsoft Windows Server 2022-datacenter-g2
Launch Method: SSH
JDK: 21.0.5 +11 LTS (From Temurin package)
Reproduction steps
Configure an agent template with the "Azure VM Idle Retention Strategy" and a timeout of 5 minutes
Wait for a build to run
Wait for 5 minutes after the build completes
Expected Results
The agent should be marked as "Offline" and then deprovisioned in Azure via the Azure VM Agents Plugin.
Actual Results
The agent instead sits in the "Offline" state in Jenkins, while the actual VM in Azure is deleted. This causes the plugin to hit its max agents limit, and queue jobs indefinitely without trying to start new VMs to process jobs.
Anything else?
The only thing I've been able to track down on this are a bulleted error message from the "Clouds" overview page:
* Provisioning activity was completed before reaching OPERATING phase without reporting a problem
* Provisioning interrupted by restart
I don't see errors or stack traces in the com.microsoft.azure.vmagent logger, so there's nothing to dig into there. And looking through the deployments in the Azure Portal, they successfully get the deprovisioning deployment and carry it out, there's just something missing between the plugin checking the state of a VM in Azure and reporting it to the provisioned nodes in Jenkins.
Are you interested in contributing a fix?
I mean sure, but Java isn't my main strength
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Controller:
OS: Ubuntu 20.04.6 LTS
JDK: 21.0.5
Agents:
OS: Microsoft Windows Server 2022-datacenter-g2
Launch Method: SSH
JDK: 21.0.5 +11 LTS (From Temurin package)
Reproduction steps
Expected Results
The agent should be marked as "Offline" and then deprovisioned in Azure via the Azure VM Agents Plugin.
Actual Results
The agent instead sits in the "Offline" state in Jenkins, while the actual VM in Azure is deleted. This causes the plugin to hit its max agents limit, and queue jobs indefinitely without trying to start new VMs to process jobs.
Anything else?
The only thing I've been able to track down on this are a bulleted error message from the "Clouds" overview page:
I don't see errors or stack traces in the
com.microsoft.azure.vmagent
logger, so there's nothing to dig into there. And looking through the deployments in the Azure Portal, they successfully get the deprovisioning deployment and carry it out, there's just something missing between the plugin checking the state of a VM in Azure and reporting it to the provisioned nodes in Jenkins.Are you interested in contributing a fix?
I mean sure, but Java isn't my main strength
The text was updated successfully, but these errors were encountered: