[JIRA] (JENKINS-58020) agent connected via TCP but executor does not show up online sometimes

alexeygrigorov@gmail.com (JIRA)

unread,

Jun 14, 2019, 11:55:02 AM6/14/19

to jenkinsc...@googlegroups.com

Alexey Grigorov created an issue

Jenkins /

JENKINS-58020

agent connected via TCP but executor does not show up online sometimes

Issue Type:	Bug
Assignee:	Jeff Thompson
Attachments:	image-2019-06-14-18-48-15-448.png
Components:	core, remoting
Created:	2019-06-14 15:54
Environment:	Jenkins 2.164.3 , Remoting 3.29
Priority:	Critical
Reporter:	Alexey Grigorov

Hi Jenkins team/community

we started to observe that our cloud agents sometimes (roughly fail rate is 10% of launches) fail to come up online within first attempt. Here it a timeline and logs of such case:

~13:40 agent was created by cloud plugin (VMware in this case, but same problem was observed on kubernetes cloud also, so i suggest cloud type is not important)

Here is agent log

 
                                                                Jun 14, 2019 1:40:29 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using c:\remoting as a remoting work directory
Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: dev-take-onescm-build__1
Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Jenkins agent is running in headless mode.
Jun 14, 2019 1:40:30 PM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 3.29
Jun 14, 2019 1:40:30 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using c:\remoting as a remoting work directory
Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://jenkins.aureacentral.com/]
Jun 14, 2019 1:40:30 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
  Agent address: jenkins.aureacentral.com
  Agent port:    50000
  Identity:      a6:78:37:21:42:8e:c2:e1:08:e2:45:8b:83:df:c2:46
Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkins.aureacentral.com:50000
Jun 14, 2019 1:40:30 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jun 14, 2019 1:40:31 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: a6:78:37:21:42:8e:c2:e1:08:e2:45:8b:83:df:c2:46
Jun 14, 2019 1:40:32 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected 
                                                            

here is part of server log related to same agent

 
                                                                Jun 14, 2019 1:40:36 PM org.jenkinsci.plugins.vSphereCloud InternalLog
INFO: [dev-take-onescm-build__1] Slave has come online.
Jun 14, 2019 1:40:36 PM org.jenkinsci.plugins.vSphereCloud InternalLog
INFO: [dev-take-onescm-build__1] Slave online
Jun 14, 2019 1:40:37 PM org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode$1 call
INFO: Provisioned new slave dev-take-onescm-build__1
Jun 14, 2019 1:41:17 PM hudson.slaves.NodeProvisioner$2 run
INFO: dev-take-onescm-build__1 provisioning successfully completed. We have now 674 computer(s)
 
                                                            

but agent did not show up online at 13:40 as you can see on load statistic screenshot (0 executors available)

I waited 5 minutes and restarted jenkins windows service on agent VM at 13:46,

here is agent log

 
                                                                Jun 14, 2019 1:46:32 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using c:\remoting as a remoting work directory
Jun 14, 2019 1:46:32 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: dev-take-onescm-build__1
Jun 14, 2019 1:46:32 PM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Jenkins agent is running in headless mode.
Jun 14, 2019 1:46:32 PM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 3.29
Jun 14, 2019 1:46:32 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using c:\remoting as a remoting work directory
Jun 14, 2019 1:46:32 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://jenkins.aureacentral.com/]
Jun 14, 2019 1:46:32 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Jun 14, 2019 1:46:32 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
  Agent address: jenkins.aureacentral.com
  Agent port:    50000
  Identity:      a6:78:37:21:42:8e:c2:e1:08:e2:45:8b:83:df:c2:46
Jun 14, 2019 1:46:32 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jun 14, 2019 1:46:32 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkins.aureacentral.com:50000
Jun 14, 2019 1:46:32 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jun 14, 2019 1:46:32 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: a6:78:37:21:42:8e:c2:e1:08:e2:45:8b:83:df:c2:46
Jun 14, 2019 1:46:33 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected
Jun 14, 2019 1:46:36 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn
WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/
 
                                                            

Server log

 
                                                                WARNING: IOHub#1: Worker[channel:java.nio.channels.SocketChannel[connected local=/10.25.33.149:50000 remote=10.25.78.118/10.25.78.118:49686]] / Computer.threadPoolForRemoting [#147073] for dev-take-onescm-build__1 terminated
java.nio.channels.ClosedChannelException
        at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
        at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)
        at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
        at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)Jun 14, 2019 1:46:27 PM org.jenkinsci.plugins.vSphereCloud InternalLog
INFO: [dev-take-onescm-build__1] Running disconnect procedure...
Jun 14, 2019 1:46:27 PM org.jenkinsci.plugins.vSphereCloud InternalLog
INFO: [dev-take-onescm-build__1] Disconnect done.  Performing idle action NOTHING...
Jun 14, 2019 1:46:27 PM org.jenkinsci.plugins.vSphereCloud InternalLog
INFO: [dev-take-onescm-build__1] Idle action NOTHING complete.
 
                                                            

and after that agent connected and come online and started job execution , (see load statistic screenshot above)

We upgraded to 2.164.3 from 2.164.1 last week and noticed this issue but we are not 100% sure it wasn't there before upgrade.

Any Ideas or direction to troubleshoot further are appreciated

Thanks

Add Comment

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

jthompson@cloudbees.com (JIRA)

unread,

Jun 14, 2019, 1:57:02 PM6/14/19

to jenkinsc...@googlegroups.com

Jeff Thompson commented on

JENKINS-58020

Re: agent connected via TCP but executor does not show up online sometimes

An interesting and frustrating situation but I'm afraid I don't any good answers or suggestions for you.

Let me if I can summarize your situation. The agent log shows that the agent is connected. The master log shows that the agent has connected. But, the master UI is not showing the agent as connected and the system doesn't know it is connected to schedule builds on it. Does that describe it correctly?

If that's the case, it sounds like the connection is being made fine, but somehow it's not being added into all the required places inside the master. It's hard to guess what might be happening there.

I suggest combing through the master logs for anything relating to node, computer, agent, or slave to see if you can find any errors. You could try using the script console to poke around Jenkins.getNodes() and anything else related to see if you can find anything interesting.

Please report back with any results.

Add Comment

alexeygrigorov@gmail.com (JIRA)

unread,

Jun 28, 2019, 7:55:02 AM6/28/19

to jenkinsc...@googlegroups.com

Alexey Grigorov updated an issue

Jenkins /

JENKINS-58020

agent connected via TCP but executor does not show up online sometimes

Change By:	Alexey Grigorov
Attachment:	image-2019-06-28-14-54-50-188.png

Add Comment

alexeygrigorov@gmail.com (JIRA)

unread,

Jun 28, 2019, 8:03:02 AM6/28/19

to jenkinsc...@googlegroups.com

Alexey Grigorov commented on

JENKINS-58020

Re: agent connected via TCP but executor does not show up online sometimes

Last week we upgraded to 2.176.1 LTS, problem still happening

here is example on k8s this time

on 10:06 agent log says it is connected but server waits for 15 minutes it until timeout exceeded and than kill container

 
                                                                java.lang.IllegalStateException: Agent is not connected after 900 seconds, status: Running
        at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:193)
        at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294)
        at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
        at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
2019-06-28 10:21:55.279+0000 [id=13265377]      FINER   o.c.j.p.k.KubernetesLauncher#launch: Removing Jenkins node: northplains-xinet-centos6-cibuild-dmz04
 
                                                            

here https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesLauncher.java#L185

slaveComputer == null || slaveComputer.isOffline() condition is true

Add Comment

alexeygrigorov@gmail.com (JIRA)

unread,

Jun 28, 2019, 8:09:02 AM6/28/19

to jenkinsc...@googlegroups.com

Alexey Grigorov commented on

JENKINS-58020

Re: agent connected via TCP but executor does not show up online sometimes

seems in my initial post I overestimated fail rate, according to last logs I have on kubernetes fail rate is just 0.5%

Add Comment

alexeygrigorov@gmail.com (JIRA)

unread,

Jun 28, 2019, 8:10:04 AM6/28/19

to jenkinsc...@googlegroups.com

Alexey Grigorov updated an issue

Jenkins /

JENKINS-58020

agent connected via TCP but executor does not show up online sometimes

Change By:	Alexey Grigorov

Hi Jenkins team/community

we started to observe that our cloud agents sometimes (roughly fail rate is - 10% - 0.5% of launches) fail to come up online within first attempt. Here it a timeline and logs of such case:

~13:40 agent was created by cloud plugin (VMware in this case, but same problem was observed on kubernetes cloud also, so i suggest cloud type is not important)

Here is agent log

{noformat}

INFO: Connected{noformat}

here is part of server log related to same agent

{noformat}

Jun 14, 2019 1:40:36 PM org.jenkinsci.plugins.vSphereCloud InternalLog
INFO: [dev-take-onescm-build__1] Slave has come online.
Jun 14, 2019 1:40:36 PM org.jenkinsci.plugins.vSphereCloud InternalLog
INFO: [dev-take-onescm-build__1] Slave online
Jun 14, 2019 1:40:37 PM org.jenkinsci.plugins.vSphereCloud$VSpherePlannedNode$1 call
INFO: Provisioned new slave dev-take-onescm-build__1
Jun 14, 2019 1:41:17 PM hudson.slaves.NodeProvisioner$2 run
INFO: dev-take-onescm-build__1 provisioning successfully completed. We have now 674 computer(s)

{noformat}

but agent did not show up online at 13:40 as you can see on load statistic screenshot (0 executors available)

!image-2019-06-14-18-48-15-448.png|width=518,height=404!

I waited 5 minutes and restarted jenkins windows service on agent VM at 13:46,

here is agent log

{noformat}

{noformat}
Server log
{noformat}

WARNING: IOHub#1: Worker[channel:java.nio.channels.SocketChannel[connected local=/10.25.33.149:50000 remote=10.25.78.118/10.25.78.118:49686]] / Computer.threadPoolForRemoting [#147073] for dev-take-onescm-build__1 terminated
java.nio.channels.ClosedChannelException
        at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
        at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179)
        at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)
        at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
        at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)Jun 14, 2019 1:46:27 PM org.jenkinsci.plugins.vSphereCloud InternalLog
INFO: [dev-take-onescm-build__1] Running disconnect procedure...
Jun 14, 2019 1:46:27 PM org.jenkinsci.plugins.vSphereCloud InternalLog
INFO: [dev-take-onescm-build__1] Disconnect done. Performing idle action NOTHING...
Jun 14, 2019 1:46:27 PM org.jenkinsci.plugins.vSphereCloud InternalLog
INFO: [dev-take-onescm-build__1] Idle action NOTHING complete.

{noformat}

and after that agent connected and come online and started job execution , (see load statistic screenshot above)

We upgraded to 2.164.3 from 2.164.1 last week and noticed this issue but we are not 100% sure it wasn't there before upgrade.

Any Ideas or direction to troubleshoot further are appreciated

Thanks

Add Comment

alexeygrigorov@gmail.com (JIRA)

unread,

Jun 28, 2019, 8:22:01 AM6/28/19

to jenkinsc...@googlegroups.com

Alexey Grigorov updated an issue

Jenkins /

JENKINS-58020

agent connected via TCP but executor does not show up online sometimes

Change By:	Alexey Grigorov
Environment:	Jenkins 2. 164 176 . 3 1 , Remoting 3.29

Add Comment

glavenuta@alteanet.it (JIRA)

unread,

Oct 4, 2019, 6:48:02 AM10/4/19

to jenkinsc...@googlegroups.com

Giovanna Lavenuta commented on

JENKINS-58020

Re: agent connected via TCP but executor does not show up online sometimes

Hi all,

I've the same issue since yesterday. Suddenly only one type of agent of mine has stopped to work.

Have you an idea about the problem cause?

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

glavenuta@alteanet.it (JIRA)

unread,

Oct 4, 2019, 8:03:04 AM10/4/19

to jenkinsc...@googlegroups.com

Giovanna Lavenuta edited a comment on

JENKINS-58020

Re: agent connected via TCP but executor does not show up online sometimes

{noformat}
*non* viene effettuata nessun'altra _formattazione_ qui{noformat}

Hi all,

I've the same issue since yesterday. Suddenly only one type of agent of mine has stopped to work.

Have you an idea about the problem cause?

the log of the agent

{code:java}
kubectl logs worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c-l8f6b -c jnlp
Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior
Oct 04, 2019 11:58:21 AM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c-l8f6b
Oct 04, 2019 11:58:21 AM hudson.remoting.jnlp.Main$CuiListener <init>

INFO: Jenkins agent is running in headless mode.

Oct 04, 2019 11:58:21 AM hudson.remoting.Engine startEngine
INFO: Using Remoting version: 3.27
Oct 04, 2019 11:58:21 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
INFO: Using /home/jenkins/agent/remoting as a remoting work directory
Both error and output logs will be printed to /home/jenkins/agent/remoting
Oct 04, 2019 11:58:21 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [http://jenkins:8080/]
Oct 04, 2019 11:58:21 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve

INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]

Oct 04, 2019 11:58:21 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 11:58:21 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
Agent address: jenkins-agent
Agent port: 50000
Identity: 4e:a3:2e:fe:b5:3e:d1:26:ce:65:0f:3f:2c:86:9b:fc
Oct 04, 2019 11:58:21 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Oct 04, 2019 11:58:21 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkins-agent:50000
Oct 04, 2019 11:58:22 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Oct 04, 2019 11:58:22 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Remote identity confirmed: 4e:a3:2e:fe:b5:3e:d1:26:ce:65:0f:3f:2c:86:9b:fc
Oct 04, 2019 11:58:23 AM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connected{code}

the log of jenkins master
{code:java}
2019-10-04 12:00:03.143+0000 [id=4588] WARNING o.c.j.p.k.KubernetesLauncher#launch: Error in provisioning; agent=KubernetesSlave name: worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c-l8f6b, template=PodTemplate{, name='worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c', namespace='default', label='worker-bbb6979c-390b-4867-81c6-03686354689d', nodeUsageMode=EXCLUSIVE, containers=[ContainerTemplate{name='deploy-to-test', image='mycare-dev.icp:8500/default/vpn-icp-tools:latest', privileged=true, alwaysPullImage=true, command='/start.sh', resourceRequestCpu='50m', resourceRequestMemory='100Mi', resourceLimitCpu='200m', resourceLimitMemory='300Mi', envVars=[SecretEnvVar [secretName=vpn-mycare-secret, secretKey=vpnaddr, getKey()=VPNADDR], SecretEnvVar [secretName=vpn-mycare-secret, secretKey=vpnuser, getKey()=VPNUSER], SecretEnvVar [secretName=vpn-mycare-secret, secretKey=vpnpass, getKey()=VPNPASS], SecretEnvVar [secretName=vpn-mycare-secret, secretKey=vpnrdpip, getKey()=VPNRDPIP], SecretEnvVar [secretName=vpn-mycare-secret, secretKey=icpuser, getKey()=ICPUSERNAME], SecretEnvVar [secretName=vpn-mycare-secret, secretKey=icppasswd, getKey()=ICPPASSWD]]}], annotations=[org.csanchez.jenkins.plugins.kubernetes.PodAnnotation@aab9c821]}
java.lang.IllegalStateException: Agent is not connected after 100 seconds, status: Running
at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:193)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:297)

at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

2019-10-04 12:00:03.143+0000 [id=4588] INFO o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c-l8f6b
2019-10-04 12:00:03.181+0000 [id=4588] INFO o.c.j.p.k.KubernetesSlave#deleteSlavePod: Terminated Kubernetes instance for agent default/worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c-l8f6b
2019-10-04 12:00:03.181+0000 [id=4588] INFO o.c.j.p.k.KubernetesSlave#_terminate: Disconnected computer worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c-l8f6b
Terminated Kubernetes instance for agent default/worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c-l8f6b
Disconnected computer worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c-l8f6b
2019-10-04 12:00:09.146+0000 [id=24] INFO o.c.j.p.k.KubernetesCloud#provision: Excess workload after pending Kubernetes agents: 1
2019-10-04 12:00:09.146+0000 [id=24] INFO o.c.j.p.k.KubernetesCloud#provision: Template for label worker-bbb6979c-390b-4867-81c6-03686354689d: Kubernetes Pod Template
2019-10-04 12:00:19.171+0000 [id=39] INFO hudson.slaves.NodeProvisioner#lambda$update$6: Kubernetes Pod Template provisioning successfully completed. We have now 2 computer(s)
2019-10-04 12:00:19.181+0000 [id=4588] INFO o.c.j.p.k.KubernetesLauncher#launch: Created Pod: default/worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c-fjfjc
2019-10-04 12:00:19.249+0000 [id=4646] INFO o.internal.platform.Platform#log: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path?
2019-10-04 12:00:21.704+0000 [id=4588] INFO o.c.j.p.k.KubernetesLauncher#launch: Pod is running: default/worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c-fjfjc
2019-10-04 12:00:21.708+0000 [id=4588] INFO o.c.j.p.k.KubernetesLauncher#launch: Waiting for agent to connect : worker-bbb6979c-390b-4867-81c6-03686354689d-nhc1c-fjfjc{code}

Add Comment

Reply all

Reply to author

Forward