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

          Basil Crow added a comment -

          Basil Crow added a comment - vlatombe FYI

          Vincent Latombe added a comment - - edited

          This is expected to be fixed (core will print a warning, but not break) with https://github.com/jenkinsci/jenkins/pull/8448 included in 2.422.
          Seems like this plugin is not affected by the same issue.

          Vincent Latombe added a comment - - edited This is expected to be fixed (core will print a warning, but not break) with https://github.com/jenkinsci/jenkins/pull/8448 included in 2.422. Seems like this plugin is not affected by the same issue.

          Vincent Latombe added a comment - - edited

          I've taken another look, and filed https://github.com/jenkinsci/jenkins/pull/8564. As I am not able to test this particular plugin, it would be great if quacktacular could try this change against it (either by building the pull request locally, or using the incrementals build as soon as available) to verify that it indeed fixes the issue for vsphere-cloud plugin.

          Vincent Latombe added a comment - - edited I've taken another look, and filed https://github.com/jenkinsci/jenkins/pull/8564 . As I am not able to test this particular plugin, it would be great if quacktacular could try this change against it (either by building the pull request locally, or using the incrementals build as soon as available) to verify that it indeed fixes the issue for vsphere-cloud plugin.

          Basil Crow added a comment -

          Incremental build 2.427-rc34267.67cf93d3772c is available for testing. The incremental build is available from: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.427-rc34267.67cf93d3772c/

          quacktacular Can you please test the incremental build and confirm the issue is resolved?

          Basil Crow added a comment - Incremental build 2.427-rc34267.67cf93d3772c is available for testing. The incremental build is available from: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/main/jenkins-war/2.427-rc34267.67cf93d3772c/ quacktacular Can you please test the incremental build and confirm the issue is resolved?

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

              Created:
              Updated:
              Resolved: