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

Build permission on agents is not working

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Jenkins Version: 2.164.1

      Role Strategy Plugin Version: 2.10

      I configured a role with all agent related permissions: Build, Configure, Connect, Disconnect...

      With this role assigned to a user, that user can Configure the agent, but it can't run builds on it. The cause of blockage indicates it lacks permissions to run on this slave.

      It is related with the authorization strategy implementing the getACL for Computer but not for Node. If implementing the ACL also for Node apparently works without issues.

       

       

       

        Attachments

          Activity

          Hide
          samica Frederico Pratas added a comment - - edited

          I'm facing the same issue, slave A owned by user X is not accepting jobs from the user.

          The output is:

          'X' lacks permission to run on 'A'

           

          Jenkins 2.253
          Role-based Authorization Strategy v3.0

          Show
          samica Frederico Pratas added a comment - - edited I'm facing the same issue, slave A owned by user X is not accepting jobs from the user. The output is: 'X' lacks permission to run on 'A'   Jenkins 2.253 Role-based Authorization Strategy v3.0
          Hide
          tkleiber Torsten Kleiber added a comment -

          On my staging jenkins system this works fine, but not on my production system. I don't see the responsible difference in both configurations.

          Show
          tkleiber Torsten Kleiber added a comment - On my staging jenkins system this works fine, but not on my production system. I don't see the responsible difference in both configurations.
          Hide
          gradol Oliver Grad added a comment -

          A Happy New Year.

          Are there any news on this issue.

          It's still reproducable, now on Jenkins 2.274 and Role-based Authorization Strategy-Plugin 3.1.

          Show
          gradol Oliver Grad added a comment - A Happy New Year. Are there any news on this issue. It's still reproducable, now on Jenkins 2.274 and Role-based Authorization Strategy-Plugin 3.1.
          Hide
          gradol Oliver Grad added a comment -

          Found a solution for our specific case.

          Using Job Restrictions Plugin will meet our needs.

          Show
          gradol Oliver Grad added a comment - Found a solution for our specific case. Using Job Restrictions Plugin will meet our needs.
          Hide
          brianbroussard Brian added a comment -

          I am experiencing this same issue. Setting "Project Default Build Authorization" to "Run as User who triggered build" causes jobs to hang with the message "user lacks permissions to run on node"

          Show
          brianbroussard Brian added a comment - I am experiencing this same issue. Setting "Project Default Build Authorization" to "Run as User who triggered build" causes jobs to hang with the message "user lacks permissions to run on node"

            People

            Assignee:
            oleg_nenashev Oleg Nenashev
            Reporter:
            luispiedra Luis Piedra-Márquez
            Votes:
            13 Vote for this issue
            Watchers:
            21 Start watching this issue

              Dates

              Created:
              Updated: