use Role-Based Strategy.

       

      • Create a Folder "test"
      • create credentials in folder "test"
      • Create a job within the folder,Setup Kubernetes CLI (kubectl) use the credentials
      • Run job

      but: 
      ERROR: No credentials found for id "557f78f0-a2e0-4fae-a3ee-00cac16514f8"
      create credentials in system domain  it's worked.

          [JENKINS-57631] No credentials found for id

          Jesse Glick added a comment -

          Setup Kubernetes CLI (kubectl) use the credentials

          Too vague to reproduce. Perhaps a user error.

          Jesse Glick added a comment - Setup Kubernetes CLI (kubectl) use the credentials Too vague to reproduce. Perhaps a user error.

          Benjamin Brummer added a comment - - edited

          Update: Transfered jenkins again now everything is fine.

           

          After a migration from a centos to a ubuntu system we get the error "Cannot find any credentials with id..." for all projects. The jobs run fine, but it is not possible to switch credentials. I can add new one in the job configuration, but they are not select able afterwards.

          Benjamin Brummer added a comment - - edited Update: Transfered jenkins again now everything is fine.   After a migration from a centos to a ubuntu system we get the error "Cannot find any credentials with id..." for all projects. The jobs run fine, but it is not possible to switch credentials. I can add new one in the job configuration, but they are not select able afterwards.

          I can reproduce it now:

          If i configure "Access Control for Builds" under "Global Security", the credentials vanish in the job configuration. If i remove everything under "Access Control for Builds" they reappear.

          Benjamin Brummer added a comment - I can reproduce it now: If i configure "Access Control for Builds" under "Global Security", the credentials vanish in the job configuration. If i remove everything under "Access Control for Builds" they reappear.

          Jesse Glick added a comment -

          I think this is referring to KubectlBuildWrapper on freestyle projects, with the authorize-project plugin enabled. You would need to ensure that the user associated with the project has permission to use those credentials. I do not think this area is tested at all. Sounds similar to JENKINS-48437. Is there a particular way to reproduce from scratch, in a fresh Jenkins installation (say using the mock-security-realm plugin)?

          Jesse Glick added a comment - I think this is referring to KubectlBuildWrapper on freestyle projects, with the authorize-project plugin enabled. You would need to ensure that the user associated with the project has permission to use those credentials. I do not think this area is tested at all. Sounds similar to JENKINS-48437 . Is there a particular way to reproduce from scratch , in a fresh Jenkins installation (say using the mock-security-realm plugin)?

          zern king added a comment -

          jglick

           

          zern king added a comment - jglick  

            Unassigned Unassigned
            zern zern king
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: