<http://cloud.rabb.it/2h0y1T0z1A2M/Image%202018-02-19%20at%2011.08.48%20PM.png>
On Monday, February 19, 2018 at 9:02:22 PM UTC-8, Brandon wrote: > > Hello, I am trying to use the community helm chart for Jenkins and the > Kubernetes plugin 1.2 so that agents can be dynamically provisioned > according to build needs. > > Ultimately, builds are failing because the agents are not able to connect > to the master. However, I am seeing that in both the agents and master log > that they believe they have established a connection. What is going on? How > can I debug this further. > > This is using the default agent container and doing service discovery for > a Jenkins URL and tunnel according to the services in the jenkins namespace. > > k get svc -n jenkins > NAME TYPE CLUSTER-IP EXTERNAL-IP > PORT(S) AGE > jenkins-jenkins NodePort 10.233.45.129 <none> > 8080:32080/TCP 7d > jenkins-jenkins-agent ClusterIP 10.233.11.112 <none> > 50000/TCP 7d > > > #master log > INFO: Created Pod: default-37fj9 in namespace jenkins > Feb 12, 2018 11:16:32 PM > org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch > INFO: Waiting for Pod to be scheduled (0/100): default-37fj9 > Feb 12, 2018 11:16:38 PM > org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch > INFO: Waiting for agent to connect (0/100): default-37fj9 > Feb 12, 2018 11:16:39 PM > org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch > INFO: Waiting for agent to connect (1/100): default-37fj9 > Feb 12, 2018 11:16:40 PM > org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch > INFO: Waiting for agent to connect (2/100): default-37fj9 > Feb 12, 2018 11:16:41 PM > org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch > INFO: Waiting for agent to connect (3/100): default-37fj9 > Feb 12, 2018 11:16:42 PM hudson.TcpSlaveAgentListener$ConnectionHandler run > *INFO: Accepted JNLP4-connect connection #3 from /10.233.108.132:38682 > <http://10.233.108.132:38682>* > Feb 12, 2018 11:16:42 PM > org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch > INFO: Waiting for agent to connect (4/100): default-37fj9 > Feb 12, 2018 11:16:43 PM > org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch > INFO: Waiting for agent to connect (5/100): default-37fj9 > Feb 12, 2018 11:16:44 PM > org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch > INFO: Waiting for agent to connect (6/100): default-37fj9 > > > > #agent logs > INFO: Locating server among [ > http://jenkins-jenkins.jenkins.svc.cluster.local:8080/] > Feb 12, 2018 11:16:41 PM > org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve > INFO: Remoting server accepts the following protocols: [JNLP4-connect, > JNLP-connect, Ping, JNLP2-connect] > Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status > INFO: Agent discovery successful > Agent address: jenkins-jenkins-agent.jenkins.svc.cluster.local > Agent port: 50000 > Identity: 5d:e6:82:6c:06:4a:ef:96:ae:47:09:b2:cc:58:e8:0a > Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status > INFO: Handshaking > Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status > INFO: Connecting to jenkins-jenkins-agent.jenkins.svc.cluster.local:50000 > Feb 12, 2018 11:16:41 PM hudson.remoting.jnlp.Main$CuiListener status > INFO: Trying protocol: JNLP4-connect > Feb 12, 2018 11:16:43 PM hudson.remoting.jnlp.Main$CuiListener status > INFO: Remote identity confirmed: > 5d:e6:82:6c:06:4a:ef:96:ae:47:09:b2:cc:58:e8:0a > Feb 12, 2018 11:16:55 PM hudson.remoting.jnlp.Main$CuiListener status > * INFO: Connected* > > -- > Brandon Pinske > Site Reliability Engineer > Rabb.it > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e88fad60-b5f2-4f83-82c2-5e0900743839%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
