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

Vault credentials not found secret/<secret-name>

      I'm using HashCorp Vault pluging in Jenkins multibranch pipeline with Vault Token Credential configuration. Everything was fine until the newest version 2.3.0. When I updated the version from 2.2.0 to 2.3.0 all of my pipelines using vault wrapper settings start showing me in the console output of every Jenkins job the message from the summary of the issue -> Vault credentials not found secret/<secret-name> . When I go back to 2.2.0 everything works fine again. Before revert back to 2.2.0 I have changed all the steps as it is described here -> https://wiki.jenkins.io/display/JENKINS/HashiCorp+Vault+Plugin for version 2.3.0 but nothing changed.. again the same message.

      Do you guys have any ideas why this may happen ?

          [JENKINS-58947] Vault credentials not found secret/<secret-name>

          Brian Saville added a comment -

          Likely related to JENKINS-58970.

          Brian Saville added a comment - Likely related to JENKINS-58970 .

          Is there any chance for this PR to be merged soon ?

          Kristiyan Kalugerov added a comment - Is there any chance for this PR to be merged soon ?

          Upgrading to v2.3.1 allows you to set your vault engine on the Vault Configuration.
          It will default to version 2 so if it still fails you will most likely have to set it to version 1.

          If you want to know more about engine version read here: https://www.vaultproject.io/docs/secrets/kv/index.html

          Joseph Petersen (old) added a comment - Upgrading to v2.3.1 allows you to set your vault engine on the Vault Configuration. It will default to version 2 so if it still fails you will most likely have to set it to version 1. If you want to know more about engine version read here: https://www.vaultproject.io/docs/secrets/kv/index.html

            jetersen Joseph Petersen
            cerebro Kristiyan Kalugerov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: