[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title ASHOK MOHANTY commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container Thanks, able to catch the user code issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title Jesse Glick commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container ASHOK MOHANTY whatever you are seeing, it sounds like an unrelated issue, and perhaps just a user error—incorrect pod definition. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title ASHOK MOHANTY commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container With Kub ver 1.12.4 and kub-Credential 0.3.1, I am seeing this ssh-agent issue. Can you please check. [ssh-agent] Looking for ssh-agent implementation... Could not find ssh-agent: IOException: container [dind] does not exist in pod [jenkins-slave-lcmzb-0g359] Check if ssh-agent is installed and in PATH [ssh-agent] Java/JNR ssh-agent And then finally, it shows this error - [Pipeline] End of Pipeline java.io.IOException: container [dind] does not exist in pod [jenkins-slave-lcmzb-0g359] at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:435) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title Bernhard Kaszt commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container We also sometimes get the exactly same error. It often works, but randomly throws this error. And it's not clear why it fails then. There is no error message except that ssh-add failed to run. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title
Fran Garcia edited a comment on JENKINS-42582
Re: ssh-agent not applied in kubernetes container
Using version 1.3.2 most of the times it seems to work but sometimes I get the error{code:java}ERROR: Failed to run ssh-add{code}(Almost) complete log:{code:java}First time build. Skipping changelog. [Pipeline] } [Pipeline] // stage [Pipeline] container [Pipeline] { [Pipeline] withCredentials [Pipeline] { [Pipeline] withEnv [Pipeline] { [Pipeline] timeoutTimeout timeoutTimeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] stage [Pipeline] { (Test) [Pipeline] container [Pipeline] { [Pipeline] sshagent [ssh-agent] Using credentials git-repos (SSH credential for Git repos) [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78] Executing command: "ssh-agent" printf "EXITCODE %3d" $?; exit SSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22; export SSH_AUTH_SOCK; SSH_AGENT_PID=23; export SSH_AGENT_PID; echo Agent pid 23; EXITCODE 0SSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22 SSH_AGENT_PID=23 Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78] Executing command: "ssh-add" "/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key" printf "EXITCODE %3d" $?; exit EXITCODE 0EXITCODE 0Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key) Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key) [Pipeline] // sshagent [Pipeline] } [Pipeline] // containerPost containerPost stage [Pipeline] junitRecording junitRecording test results No test report files were found. Configuration error? [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Doc) Stage 'Doc' skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Lint) Stage 'Lint' skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (SonarQube) Stage 'SonarQube' skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Deploy) Stage 'Deploy' skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Declarative: Post Actions) [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withCredentials [Pipeline] } [Pipeline] // container [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // podTemplate [Pipeline] End of PipelineERROR PipelineERROR : Failed to run ssh-add Finished: FAILURE{code} Can it be a race condition?
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title
Fran Garcia commented on JENKINS-42582
Re: ssh-agent not applied in kubernetes container
Using version 1.3.2 most of the times it seems to work but sometimes I get the error ERROR: Failed to run ssh-add First time build. Skipping changelog.[Pipeline] }[Pipeline] // stage[Pipeline] container[Pipeline] {[Pipeline] withCredentials[Pipeline] {[Pipeline] withEnv[Pipeline] {[Pipeline] timeoutTimeout set to expire in 1 hr 0 min[Pipeline] {[Pipeline] stage[Pipeline] { (Test)[Pipeline] container[Pipeline] {[Pipeline] sshagent[ssh-agent] Using credentials git-repos (SSH credential for Git repos) [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78] Executing command: "ssh-agent" printf "EXITCODE %3d" $?; exit SSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22; export SSH_AUTH_SOCK; SSH_AGENT_PID=23; export SSH_AGENT_PID; echo Agent pid 23; EXITCODE 0SSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22 SSH_AGENT_PID=23 Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78] Executing command: "ssh-add" "/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key" printf "EXITCODE %3d" $?; exit EXITCODE 0EXITCODE 0Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key) Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key)[Pipeline] // sshagent[Pipeline] }[Pipeline] // containerPost stage[Pipeline] junitRecording test results No test report files were found. Configuration error?[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Doc)Stage 'Doc' skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Lint)Stage 'Lint' skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (SonarQube)Stage 'SonarQube' skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Deploy)Stage 'Deploy' skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // podTemplate[Pipeline] End of PipelineERROR: Failed to run ssh-add Finished: FAILURE Can it be a race condition?
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title
Fran Garcia edited a comment on JENKINS-42582
Re: ssh-agent not applied in kubernetes container
Using version 1.3.2 most of the times it seems to work but sometimes I get the error {code:java} ERROR: Failed to run ssh-add {code} (Almost) complete log:{code:java} First time build. Skipping changelog. {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a} [Pipeline] container {color}{color:#9a} [Pipeline] \ { {color}{color:#9a} [Pipeline] withCredentials {color}{color:#9a} [Pipeline] \ { {color}{color:#9a} [Pipeline] withEnv {color}{color:#9a} [Pipeline] \ { {color}{color:#9a} [Pipeline] timeout{color}Timeout timeoutTimeout set to expire in 1 hr 0 min {color:#9a} [Pipeline] \ { {color}{color:#9a} [Pipeline] stage {color}{color:#9a} [Pipeline] \ { (Test) {color}{color:#9a} [Pipeline] container {color}{color:#9a} [Pipeline] \ { {color}{color:#9a} [Pipeline] sshagent {color} [ssh-agent] Using credentials git-repos (SSH credential for Git repos)[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78]Executing command: "ssh-agent" printf "EXITCODE %3d" $?; exitSSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22; export SSH_AUTH_SOCK;SSH_AGENT_PID=23; export SSH_AGENT_PID;echo Agent pid 23;EXITCODE 0SSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22SSH_AGENT_PID=23Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78]Executing command: "ssh-add" "/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key" printf "EXITCODE %3d" $?; exitEXITCODE 0EXITCODE 0Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key)Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key) {color:#9a} [Pipeline] // sshagent {color}{color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // container{color}Post containerPost stage {color:#9a} [Pipeline] junit{color}Recording junitRecording test resultsNo test report files were found. Configuration error? {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a} [Pipeline] stage {color}{color:#9a} [Pipeline] \ { (Doc) {color} Stage 'Doc' skipped due to earlier failure(s) {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a} [Pipeline] stage {color}{color:#9a} [Pipeline] \ { (Lint) {color} Stage 'Lint' skipped due to earlier failure(s) {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a} [Pipeline] stage {color}{color:#9a} [Pipeline] \ { (SonarQube) {color} Stage 'SonarQube' skipped due to earlier failure(s) {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a} [Pipeline] stage {color}{color:#9a} [Pipeline] \ { (Deploy) {color} Stage 'Deploy' skipped due to earlier failure(s) {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a} [Pipeline]
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title Dániel Szoboszlay commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container Thank you Matthew Ludlum, this is awesome! Everything is working fine now with version 1.3.2. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title Carlos Sanchez resolved as Fixed Jenkins / JENKINS-42582 ssh-agent not applied in kubernetes container Change By: Carlos Sanchez Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title Matthew Ludlum started work on JENKINS-42582 Change By: Matthew Ludlum Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title Matthew Ludlum commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container I think I have found a solution for this - we can use override the computer getEnvironment to drop the computer level properties(JAVA_HOME, etc) and use the built in variables without issue. This would avoid the need for workarounds. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title Jesse Glick commented on JENKINS-42582 Re: ssh-agent not applied in kubernetes container Sounds like the more general issue JENKINS-49370. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title
J Knurek commented on JENKINS-42582
Re: ssh-agent not applied in kubernetes container
one thing I saw in the logs, is that if `sshagent () {}` is the first command in the container (like the example above), the workspace isn't created yet
[ssh-agent] Using credentials jenkins-master-ssh
[ssh-agent] Looking for ssh-agent implementation...
Executing shell script inside container [golang] of pod [kubernetes-6f33c7fc5ad644b]
Executing command: ssh-agent -k
# cd "/home/jenkins/workspace/ssh-fail"
ssh-agent -k
exit
/bin/sh: 1: cd: can't cd to /home/jenkins/workspace/ssh-fail
# SSH_AGENT_PID not set, cannot kill agent
fixing that , the ssh-agent plugin still doesn't provide the key as expected
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title
J Knurek created an issue
Jenkins / JENKINS-42582
ssh-agent not applied in kubernetes container
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin, ssh-agent-plugin
Created:
2017/Mar/08 2:21 PM
Priority:
Major
Reporter:
J Knurek
the ssh-agent configuration isn't applied when pipeline is run on a docker container using the kubernetes plugin as an example, this pipeline works fine:
sshagent in basic pipeline
node {
stage('Pre-Build') {
sshagent (credentials: ['jenkins-master-ssh']) {
sh 'ssh -vT -o "StrictHostKeyChecking=no" g...@github.com'
}
}
}
the job will fail, but the console output will clearly show the error from github
You've successfully authenticated, but GitHub does not provide shell access.
whereas
sshagent not applied in container
podTemplate(label: 'jenkpod', containers: [containerTemplate(name: 'golang', image: 'golang:1.8', ttyEnabled: true, command: 'cat')]
