[JIRA] (JENKINS-49511) Connection fails between agent and master
Title: Message Title Carlos Sanchez closed an issue as Not A Defect Feel free to submit a PR to improve docs https://github.com/jenkinsci/kubernetes-plugin/#constraints Jenkins / JENKINS-49511 Connection fails between agent and master Change By: Carlos Sanchez Status: Open Closed Resolution: Not A Defect 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
[JIRA] (JENKINS-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master Ok I seem to have missed it then. Could it be in jenkins itself? At the moment the name field for the container doesn't have a help text. I think it would be really useful to add it there 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-49511) Connection fails between agent and master
Title: Message Title Carlos Sanchez commented on JENKINS-49511 Re: Connection fails between agent and master It's in the docs already 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-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master I think it would be useful to add to the documentation that the name of the container for the jnpl agent must be named jnlp. This issue was quite hard to debug 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-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master This was related to this issue. If the name of the custom agent is not `jnlp`, then another agent with the default jnlp image is created. This explains messages like `channel already closed` etc.. 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-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master Actually it works if I revert back to JNLP-2. Is there any pointers I could look at that would block JNLP-4 inside kubernetes? 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-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai created an issue Jenkins / JENKINS-49511 Connection fails between agent and master Issue Type: Bug Assignee: Carlos Sanchez Attachments: logs-from-jnlp-in-slave-with-docker-g2k77.txt, logs-from-master-in-jenkins-67b96c6474-6m6wt.txt Components: kubernetes-plugin Created: 2018-02-12 16:39 Environment: Jenkins: 2.105 Kubernetes-plugin: 1.2 Priority: Major Reporter: Cesar Tron-Lozai I've set up Jenkins to run on a k8s cluster. I'm using the kubernetes plugin to create agent in the cluster. I have a discovery service available at jenkins-discovery.jenkins.svc.cluster.local:5. I've set up the tunnel property to jenkins-discovery.jenkins.svc.cluster.local:5 When I start a job, the agent seems to be able to connect but then fails for some unknown reasons. The agent logs: INFO: Locating server among [http://jenkins-internal.jenkins.svc.cluster.local:8080/] Feb 12, 2018 4:08:37 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Feb 12, 2018 4:08:37 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: jenkins-discovery.jenkins.svc.cluster.local Agent port: 5 Identity: a1:e6:e0:d2:ad:30:2e:11:47:4f:0f:95:41:d3:d0:a4 Feb 12, 2018 4:08:37 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Feb
