[JIRA] (JENKINS-60591) checkout scm doesn't take revision that started the pipeline
Title: Message Title
Mykhailo Zolotarenko updated an issue
Jenkins / JENKINS-60591
checkout scm doesn't take revision that started the pipeline
Change By:
Mykhailo Zolotarenko
+ _{color:#172b4d} Pipeline job{color}_+_{color:#172b4d} checkout scm{color}_ doesn't take revision that started the pipeline instead takes last (fresh) commit from branch Related to doc:[https://jenkins.io/doc/book/pipeline/jenkinsfile/]|The {{checkout}} step will checkout code from source control; {{scm}} is a special variable which instructs the {{checkout}} step to clone the specific revision which triggered this Pipeline run.| To reproduce: * Merge to branch (abc) * start pipeline * pipeline waits for continue (input message) * push new change to branch (xyz) * resume pipelineExpect: * pipeline resume abcObserve: * pipeline resume xyz Workaround for as - use explicit checkout git commitvariable _GIT_COMMIT_ we defined at the beginning of Pipeline: def scmVars = checkout scm env.GIT_COMMIT = scmVars.GIT_COMMIT And we see that checkout show different results: {code:java}checkout scm: [$class: 'GitSCM', branches: [[name: "${GIT_COMMIT}"]]]sh 'cat new_files'// abc{code} {code:java}checkout scmsh 'cat new_files'// xyz{code} It's a bug or feature? according to the doc - bug... (git plugin?) Can be related with JENKINS-59071 or JENKINS-43761
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60591) checkout scm doesn't take revision that started the pipeline
Title: Message Title Mykhailo Zolotarenko updated an issue Jenkins / JENKINS-60591 checkout scm doesn't take revision that started the pipeline Change By: Mykhailo Zolotarenko Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203813.1577382573000.371.1577431440462%40Atlassian.JIRA.
[JIRA] (JENKINS-60591) checkout scm doesn't take revision that started the pipeline
Title: Message Title Mykhailo Zolotarenko updated an issue Jenkins / JENKINS-60591 checkout scm doesn't take revision that started the pipeline Change By: Mykhailo Zolotarenko Environment: Jenkins 2.176.4, git-plugin 3.12.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203813.1577382573000.370.1577431440438%40Atlassian.JIRA.
[JIRA] (JENKINS-60591) checkout scm doesn't take revision that started the pipeline
Title: Message Title Mykhailo Zolotarenko created an issue Jenkins / JENKINS-60591 checkout scm doesn't take revision that started the pipeline Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-12-26 17:49 Priority: Minor Reporter: Mykhailo Zolotarenko checkout scm doesn't take revision that started the pipeline instead takes last (fresh) commit from branch Related to doc: https://jenkins.io/doc/book/pipeline/jenkinsfile/ The checkout step will checkout code from source control; scm is a special variable which instructs the checkout step to clone the specific revision which triggered this Pipeline run. To reproduce: Merge to branch (abc) start pipeline pipeline waits for continue (input message) push new change to branch (xyz) resume pipeline Expect: pipeline resume abc Observe:
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title
Mykhailo Zolotarenko edited a comment on JENKINS-53427
Re: Agent creation failure because of concurrent attempts to schedule a pod
Additional logs to the previous comment from Dan Alvizu Full JNLP container logs:{code:java}Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: ui-pipeline-shared-jbr6lOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 09, 2019 8:58:32 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.29Oct 09, 2019 8:58:32 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [https://jenkins-icecream.some.tools/]Oct 09, 2019 8:58:32 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, some]Oct 09, 2019 8:58:32 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability checkOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins-icecream-agent.some.tools Agent port: 5 Identity: 11:11:11:11:11:11:11:11:11:11:11:11:11Oct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins-icecream-agent.some.tools:5Oct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 54:90:09:b3:21:36:c7:d1:0d:3f:a6:b4:51:2c:12:61Oct 09, 2019 8:58:32 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to jenkins-icecream-agent.some.tools/10.75.115.45:5] Local headers refused by remote: Unknown client name: ui-pipeline-shared-jbr6lOct 09, 2019 8:58:32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-jbr6l at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-jbr6l at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONet
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title Mykhailo Zolotarenko commented on JENKINS-53427 Re: Agent creation failure because of concurrent attempts to schedule a pod I can reproduce this issue when I disable “Do not allow concurrent builds” and run pipeline job for couple times at the same time Our agent using kub2iam and I don’t know when and why Jenkins-master had refused the connection as it had an 'unknown client name’… maybe this is due to kub2iam, which we use for our agent… maybe something else... 1. Enable option “Do not allow concurrent builds” - this should help prevent this issue. 2. Deleting Error pods - should help prevent reaching the maximum pod limit in the kubernetes cluster 3. Stop current job - should prevent to generate Error pods… I hope this helps Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193618.1536147614000.4840.1570712640398%40Atlassian.JIRA.
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title
Mykhailo Zolotarenko edited a comment on JENKINS-53427
Re: Agent creation failure because of concurrent attempts to schedule a pod
Additional logs to the previous comment from Dan Alvizu Full JNLP container logs:{code:java}Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorOct 04 09 , 2019 9 8 : 36 58 : 28 32 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: ui-pipeline-shared- gqllt jbr6l Oct 04 09 , 2019 9 8 : 36 58 : 28 32 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 04 09 , 2019 9 8 : 36 58 : 28 32 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.29Oct 04 09 , 2019 9 8 : 36 58 : 28 32 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsOct 04 09 , 2019 9 8 : 36 58 : 29 32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [https://jenkins -icecream . example some . com tools /]Oct 04 09 , 2019 9 8 : 36 58 : 29 32 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping some ]Oct 04 09 , 2019 9 8 : 36 58 : 29 32 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability checkOct 04 09 , 2019 9 8 : 36 58 : 29 32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins -icecream-agent . example some . com tools Agent port: 5 Identity: 11:11:11:11:11:11:11:11:11:11:11:11:11 :11:11:11 Oct 04 09 , 2019 9 8 : 36 58 : 29 32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingOct 04 09 , 2019 9 8 : 36 58 : 29 32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins -icecream-agent . example some . com tools :5Oct 04 09 , 2019 9 8 : 36 58 : 29 32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectOct 04 09 , 2019 9 8 : 36 58 : 29 32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 11 54 : 11 90 : 11 09 : 11 b3 : 11 21 : 11 36 : 11 c7 : 11 d1 : 11 0d : 11 3f : 11 a6 : 11 b4 : 11 51 : 11 2c : 11 12 : 11 61 Oct 04 09 , 2019 9 8 : 36 58 : 29 32 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to jenkins -icecream-agent . example some . com tools /10.75. 105 115 . 201 45 :5] Local headers refused by remote: Unknown client name: ui-pipeline-shared- gqllt jbr6l Oct 04 09 , 2019 9 8 : 36 58 : 29 32 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared- gqllt jbr6l at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared- gqllt jbr6l at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title
Mykhailo Zolotarenko edited a comment on JENKINS-53427
Re: Agent creation failure because of concurrent attempts to schedule a pod
Additional logs to the previous comment from Dan Alvizu Full JNLP container logs:{code:java}Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorOct 04, 2019 9:36:28 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: ui-pipeline-shared-gqlltOct 04, 2019 9:36:28 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 04, 2019 9:36:28 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.29Oct 04, 2019 9:36:28 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [https://jenkins.example.com/]Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability checkOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins.example.com Agent port: 5 Identity: 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins.example.com:5Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to jenkins.example.com/10.75.105.201:5] Local headers refused by remote: Unknown client name: ui-pipeline-shared-gqlltOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-gqllt at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-gqllt at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247) at java.util.concurr
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title
Mykhailo Zolotarenko edited a comment on JENKINS-53427
Re: Agent creation failure because of concurrent attempts to schedule a pod
Additional logs to the previous comment from Dan Alvizu Full JNLP container logs:{code:java}Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorOct 04, 2019 9:36:28 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: ui-pipeline-shared-gqlltOct 04, 2019 9:36:28 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 04, 2019 9:36:28 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.29Oct 04, 2019 9:36:28 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [https://jenkins.example.com/]Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability checkOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins -icecream-agent . pingdev example . tools com Agent port: 5 Identity: 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins.example.com:5Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to jenkins.example.com/10.75.105.201:5] Local headers refused by remote: Unknown client name: ui-pipeline-shared-gqlltOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-gqllt at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-gqllt at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkL
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title
Mykhailo Zolotarenko edited a comment on JENKINS-53427
Re: Agent creation failure because of concurrent attempts to schedule a pod
Additional logs to the previous comment from Dan Alvizu Full JNLP container logs:{code:java}Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorOct 04, 2019 9:36:28 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: ui-pipeline-shared-gqlltOct 04, 2019 9:36:28 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 04, 2019 9:36:28 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.29Oct 04, 2019 9:36:28 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [https://jenkins -icecream . pingdev example . tools com /]Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability checkOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins-icecream-agent.pingdev.tools Agent port: 5 Identity: 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins -icecream-agent . pingdev example . tools com :5Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to jenkins -icecream-agent . pingdev example . tools com /10.75.105.201:5] Local headers refused by remote: Unknown client name: ui-pipeline-shared-gqlltOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-gqllt at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-gqllt at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:4
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title
Mykhailo Zolotarenko edited a comment on JENKINS-53427
Re: Agent creation failure because of concurrent attempts to schedule a pod
Addition Additional logs to the previous comment from Dan Alvizu Full JNLP container logs: {code:java}Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorOct 04, 2019 9:36:28 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: ui-pipeline-shared-gqlltOct 04, 2019 9:36:28 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 04, 2019 9:36:28 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.29Oct 04, 2019 9:36:28 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [https://jenkins-icecream.pingdev.tools/]Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability checkOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins-icecream-agent.pingdev.tools Agent port: 5 Identity: 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins-icecream-agent.pingdev.tools:5Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to jenkins-icecream-agent.pingdev.tools/10.75.105.201:5] Local headers refused by remote: Unknown client name: ui-pipeline-shared-gqlltOct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-gqllt at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-gqllt at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.imp
[JIRA] (JENKINS-53427) Agent creation failure because of concurrent attempts to schedule a pod
Title: Message Title Mykhailo Zolotarenko commented on JENKINS-53427 Re: Agent creation failure because of concurrent attempts to schedule a pod Addition to the previous comment from Dan Alvizu Full JNLP container logs: Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior Oct 04, 2019 9:36:28 AM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: ui-pipeline-shared-gqllt Oct 04, 2019 9:36:28 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Oct 04, 2019 9:36:28 AM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.29 Oct 04, 2019 9:36:28 AM hudson.remoting.Engine startEngine WARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jars Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [https://jenkins-icecream.pingdev.tools/] Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability check Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: jenkins-icecream-agent.pingdev.tools Agent port: 5 Identity: 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11 Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to jenkins-icecream-agent.pingdev.tools:5 Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP4-connect Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Remote identity confirmed: 11:11:11:11:11:11:11:11:11:11:11:11:11:11:11:11 Oct 04, 2019 9:36:29 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv INFO: [JNLP4-connect connection to jenkins-icecream-agent.pingdev.tools/10.75.105.201:5] Local headers refused by remote: Unknown client name: ui-pipeline-shared-gqllt Oct 04, 2019 9:36:29 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Protocol JNLP4-connect encountered an unexpected exception java.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-gqllt at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223) at hudson.remoting.Engine.innerRun(Engine.java:614) at hudson.remoting.Engine.run(Engine.java:474) Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: ui-pipeline-shared-gqllt at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.rem
