Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Cannot Reproduce
    • Component/s: ci
    • Labels:
      None
    • Similar Issues:

      Description

      There are about 15 Windows 2012 agents connected to ci.jenkins.io, all of which are marked offline. Some builds have apparently been waiting for them for >3½h now.

      The agents all say

      This agent is offline because Jenkins failed to launch the agent process on it.

      which sounds different from INFRA-2075.

        Attachments

          Issue Links

            Activity

            Hide
            olblak Olivier Vernin added a comment -

            Thanks for reporting, it appears right now that we both have working and none working windows agents.
            6 are displayed on the azure portal, while 21 windows agent are displayed on ci.j.io.

            I suspect ci.jenkins.io didn't cleanup its node queue and we end up with 15 undead agents

            Show
            olblak Olivier Vernin added a comment - Thanks for reporting, it appears right now that we both have working and none working windows agents. 6 are displayed on the azure portal, while 21 windows agent are displayed on ci.j.io. I suspect ci.jenkins.io didn't cleanup its node queue and we end up with 15 undead agents
            Hide
            jglick Jesse Glick added a comment -

            Maybe an issue should be filed for the Azure cloud plugin you are using to automatically delete agent definitions which do not have a corresponding live VM, similar to what I am trying to do for Kubernetes in JENKINS-49707?

            (Of course, with Windows container support coming to AKS, it would be great to just switch ci.jenkins.io to the kubernetes plugin, assuming we do JENKINS-57256.)

            Show
            jglick Jesse Glick added a comment - Maybe an issue should be filed for the Azure cloud plugin you are using to automatically delete agent definitions which do not have a corresponding live VM, similar to what I am trying to do for Kubernetes in JENKINS-49707 ? (Of course, with Windows container support coming to AKS, it would be great to just switch ci.jenkins.io to the kubernetes plugin, assuming we do JENKINS-57256 .)

              People

              • Assignee:
                olblak Olivier Vernin
                Reporter:
                jglick Jesse Glick
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: