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

0 views
Skip to first unread message

kkkalugerov@abv.bg (JIRA)

unread,
Aug 15, 2019, 7:57:02 AM8/15/19
to jenkinsc...@googlegroups.com
Kristiyan Kalugerov created an issue
 
Jenkins / Task JENKINS-58947
Vault credentials not found secret/<secret-name>
Issue Type: Task Task
Assignee: Peter Tierno
Components: hashicorp-vault-plugin
Created: 2019-08-15 11:56
Labels: plugin jenkins pipeline vault not-found
Priority: Major Major
Reporter: Kristiyan Kalugerov

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 ?

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

kkkalugerov@abv.bg (JIRA)

unread,
Aug 15, 2019, 7:58:02 AM8/15/19
to jenkinsc...@googlegroups.com
Kristiyan Kalugerov updated an issue
Change By: Kristiyan Kalugerov
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 ?

bksaville@gmail.com (JIRA)

unread,
Aug 16, 2019, 3:39:03 PM8/16/19
to jenkinsc...@googlegroups.com

kkkalugerov@abv.bg (JIRA)

unread,
Aug 19, 2019, 3:25:03 AM8/19/19
to jenkinsc...@googlegroups.com

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

josephp90@gmail.com (JIRA)

unread,
Aug 20, 2019, 12:45:02 AM8/20/19
to jenkinsc...@googlegroups.com
Joseph Petersen resolved as Fixed
 
Change By: Joseph Petersen
Status: Open Resolved
Assignee: Peter Tierno Joseph Petersen
Resolution: Fixed
Released As: https://github.com/jenkinsci/hashicorp-vault-plugin/releases/tag/hashicorp-vault-plugin-2.3.1

josephp90@gmail.com (JIRA)

unread,
Aug 20, 2019, 12:45:03 AM8/20/19
to jenkinsc...@googlegroups.com
Joseph Petersen commented on Task JENKINS-58947
 
Re: Vault credentials not found secret/<secret-name>

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

josephp90@gmail.com (JIRA)

unread,
Mar 7, 2020, 1:07:44 AM3/7/20
to jenkinsc...@googlegroups.com
Joseph Petersen assigned an issue to Joseph Petersen
 
Change By: Joseph Petersen
Assignee: Joseph Petersen (old)
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages