Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-56824

VMs not cleaned up per retention policy when they are in a failed provisioning state.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • _unsorted
    • None
    • Azure VM Agents 0.9.0, Jenkins 2.164.1

      This has happened a couple of times on ci.j.io. For whatever reason, we're not entirely sure, the init script for our Windows VMs sometimes fails.

      As a result, the agents are provisioned in Azure, but Jenkins fails to launch the JNLP agent on the machines. Unfortunately, Jenkins doesn't clean up these resources properly using our 20 minute idle retention policy.

      I discovered this morning that we had 50 VMs online for quite a few days, which never executed a single workload because their init script failed to run, and they were not cleaned up properly by the plugin.

            jieshe Jie Shen
            rtyler R. Tyler Croy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: