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

Concurrency limit not calculated over template anymore in 1.27.1

    • 1.27.1.1

      With the latest release, most likely since JENKINS-59959, the concurrency limit is no longer checked against the pod templates count. I have multiple pod templates in my environment and in 1.26.4 the concurrency limit is correctly calculated per template - in 1.27.1 i don't get my pods spawned anymore as the limit of the template is checked against the total number of pods. At least that's how it looks to me after a lot of testing

       

      Reproduction:

      add at least 2 pod templates

      set a concurrency limit of 1 on  the first and a higher one on the other

      concurrency for the whole cluster above the two limits

      spawn some pods of the second template

      -> a job requiring a pod of template one does not spawn until no other pods are live

          [JENKINS-63705] Concurrency limit not calculated over template anymore in 1.27.1

          Sledge Sulaweyo created issue -
          Sledge Sulaweyo made changes -
          Description Original: With the latest release, most likely since JENKINS-59959, the concurrency limit is no longer checked against the pod templates count. I have multiple pod templates in my environment and in 1.26.4 the concurrency limit is correctly calculated per template - in 1.27.1 i don't get my pods spawned anymore as the limit of the template is checked against the total number of pods. At least that's how it looks to me after a lot of testing New: With the latest release, most likely since JENKINS-59959, the concurrency limit is no longer checked against the pod templates count. I have multiple pod templates in my environment and in 1.26.4 the concurrency limit is correctly calculated per template - in 1.27.1 i don't get my pods spawned anymore as the limit of the template is checked against the total number of pods. At least that's how it looks to me after a lot of testing

           

          Reproduction:

          ad at least 2 pod templates

          set a concurrency limit of 1 on  the first and a higher one on the other

          concurrency for cluster above the two limits

          spawn pods of the second template

          -> a job requiring a pod of template one does not spawn
          Sledge Sulaweyo made changes -
          Description Original: With the latest release, most likely since JENKINS-59959, the concurrency limit is no longer checked against the pod templates count. I have multiple pod templates in my environment and in 1.26.4 the concurrency limit is correctly calculated per template - in 1.27.1 i don't get my pods spawned anymore as the limit of the template is checked against the total number of pods. At least that's how it looks to me after a lot of testing

           

          Reproduction:

          ad at least 2 pod templates

          set a concurrency limit of 1 on  the first and a higher one on the other

          concurrency for cluster above the two limits

          spawn pods of the second template

          -> a job requiring a pod of template one does not spawn
          New: With the latest release, most likely since JENKINS-59959, the concurrency limit is no longer checked against the pod templates count. I have multiple pod templates in my environment and in 1.26.4 the concurrency limit is correctly calculated per template - in 1.27.1 i don't get my pods spawned anymore as the limit of the template is checked against the total number of pods. At least that's how it looks to me after a lot of testing

           

          Reproduction:

          ad at least 2 pod templates

          set a concurrency limit of 1 on  the first and a higher one on the other

          concurrency for cluster above the two limits

          spawn pods of the second template

          -> a job requiring a pod of template one does not spawn until no other pods are live
          Sledge Sulaweyo made changes -
          Description Original: With the latest release, most likely since JENKINS-59959, the concurrency limit is no longer checked against the pod templates count. I have multiple pod templates in my environment and in 1.26.4 the concurrency limit is correctly calculated per template - in 1.27.1 i don't get my pods spawned anymore as the limit of the template is checked against the total number of pods. At least that's how it looks to me after a lot of testing

           

          Reproduction:

          ad at least 2 pod templates

          set a concurrency limit of 1 on  the first and a higher one on the other

          concurrency for cluster above the two limits

          spawn pods of the second template

          -> a job requiring a pod of template one does not spawn until no other pods are live
          New: With the latest release, most likely since JENKINS-59959, the concurrency limit is no longer checked against the pod templates count. I have multiple pod templates in my environment and in 1.26.4 the concurrency limit is correctly calculated per template - in 1.27.1 i don't get my pods spawned anymore as the limit of the template is checked against the total number of pods. At least that's how it looks to me after a lot of testing

           

          Reproduction:

          add at least 2 pod templates

          set a concurrency limit of 1 on  the first and a higher one on the other

          concurrency for the whole cluster above the two limits

          spawn some pods of the second template

          -> a job requiring a pod of template one does not spawn until no other pods are live
          David Schott made changes -
          Assignee New: David Schott [ shott85 ]
          Jesse Glick made changes -
          Link New: This issue is caused by JENKINS-59959 [ JENKINS-59959 ]
          Jesse Glick made changes -
          Labels New: regression
          Vincent Latombe made changes -
          Released As New: 1.27.1.1
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

            shott85 David Schott
            sulaweyo Sledge Sulaweyo
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: