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

Jenkins 2.421 breaks vSphere Cloud agent labels

    • 2.427, 2.426.1

      The latest version of Jenkins appears to have updated agent / label management in a way that prevents the vSphere Cloud Plugin from setting labels on created agents. Agents are created, run, and become ready – but jobs are never started because labels are not set. 

      Downgrading to Jenkins 2.420 immediately resolves the issue. 

      Was not able to find any logs regarding trouble getting labels, but please let me know if there is something specific I can search for. I will update if I find anything.

      What's new in 2.421 (2023-08-29)

      • Optimize performance of label parsing. (pull 8395)

          [JENKINS-71937] Jenkins 2.421 breaks vSphere Cloud agent labels

          Brendan created issue -
          Brendan made changes -
          Description Original: The latest version of Jenkins appears to have updated agent / label management in a way that prevents the vSphere Cloud Plugin from setting labels on created agents. Agents are created, run, and become ready – but jobs are never started because labels are not set. 

          Downgrading to Jenkins 2.420 immediately resolves the issue. 
          h3. What's new in 2.421 (2023-08-29)
          6 !https://www.jenkins.io/images/changelog/sunny.svg! 0 !https://www.jenkins.io/images/changelog/cloudy.svg! 7 !https://www.jenkins.io/images/changelog/storm.svg! * Add a nicer 404 error page. (issue 71087)
           * Add appearance system configuration page. ([pull 8403|https://github.com/jenkinsci/jenkins/pull/8403])
           * Optimize performance of label parsing. ([pull 8395|https://github.com/jenkinsci/jenkins/pull/8395])
           * Fix invalid CSS which caused some buttons to become invisible on hover. (issue 71479)
           * Message no longer appears twice when the {{agentLog}} option is used. (issue 38520)
          New: The latest version of Jenkins appears to have updated agent / label management in a way that prevents the vSphere Cloud Plugin from setting labels on created agents. Agents are created, run, and become ready – but jobs are never started because labels are not set. 

          Downgrading to Jenkins 2.420 immediately resolves the issue. 

          _Was not able to find any logs regarding trouble getting labels, but please let me know if there is something specific I can search for. I will update if I find anything._
          h3. What's new in 2.421 (2023-08-29)
           * Optimize performance of label parsing. ([pull 8395|https://github.com/jenkinsci/jenkins/pull/8395])
          Basil Crow made changes -
          Labels New: regression
          Vincent Latombe made changes -
          Assignee New: Vincent Latombe [ vlatombe ]
          Vincent Latombe made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Vincent Latombe made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Vincent Latombe made changes -
          Labels Original: regression New: lts-candidate regression
          Alexander Brandes made changes -
          Remote Link New: This issue links to "https://github.com/jenkinsci/jenkins/pull/8564 (Web Link)" [ 28963 ]
          Vincent Latombe made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Fixed but Unreleased [ 10203 ]
          Alexander Brandes made changes -
          Released As New: 2.427
          Status Original: Fixed but Unreleased [ 10203 ] New: Closed [ 6 ]
          Mark Waite made changes -
          Labels Original: lts-candidate regression New: 2.426.1-fixed regression

            vlatombe Vincent Latombe
            quacktacular Brendan
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: