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

Azure VM agents disconnected and deprovisioned mid-build

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • _unsorted
    • None

      **Actual behavior

      Agents provisioned by plugin were disconnected mid-build

       

      Expected behavior

      **Agents provisioned by plugin are not disconnected mid-build.

       

      Details

      We've recently (~1 month) started using the Azure VM Agents plugin mainly as a means to reduce the cost of our CI deployment which is growing quite large. This afternoon, all of a sudden, all agents provisioned by the plugin were disconnected while most of them were still in the middle of building. For us, this is a complete catastrophe as it means that we're effectively unable to verify any type of change to our git repos as we rely on the ability to quickly and effectively gate every single commit. Our own investigations have turned up blank as there isn't the slightest hint of errors in the relevant logs. The only possibly relevant configuration change was that our Windows Infra team added a testing template to evaluate the plugin for Windows custom images. The templates (ubuntu and windows) share the same cloud configuration (thus using the same resource group) and use the same storage account. Otherwise they are different in every way.

      Please let us know if any more information is required, preferrably by mail if possible. We will gladly and in the speediest of manners comply with any such requests.

       

      Attachments

      Screenshot showing the state of the provisioned agents in the cloud statistics view

      Screenshot showing the state of the provisioned agents in the node list

      Last 24h worth of Jenkins logs related to Azure with 20 lines of context after grep match

            jieshe Jie Shen
            emanuel_tobiitech Emanuel Birge
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: