-
Bug
-
Resolution: Cannot Reproduce
-
Minor
-
osx sierra
minikube version: v0.18.0
jenkins official container 2.46.2
kubernetes plugin 0.11
default jnlp container
Hi, I'm running kubernetes locally on my mac via minikube to test out using the kubernetes plugin. I seem to be running into an issue when the jnlp container attempts to connect back to the jenkins master, it seems to discover it fine, but then the fails with "None of the protocols were accepted". I also tested if there was connectivity on port the jnlp port 50000 which is open so I'm some what a loss what the issue could be.
I've attached the the logs and dashboard/env var information for the jnlp container, and the jenkins logs.
I'm pretty new to kubernetes and the remoting part of jenkins but these line stick out to me
INFO: Accepted connection #15 from /172.17.0.1:39604
May 04, 2017 1:25:31 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv
INFO: [JNLP4-connect connection from /172.17.0.1:39604] Refusing headers from remote: Unknown client name: kubernetes-8bc92b750f5b4427a1d25963f95474e4-6673e16106d
Thanks for any insight you can provide. If there's anything else I can provide just let me know.
- is duplicated by
-
JENKINS-48470 Unknown client name for JNLP4-connect
- Resolved
-
JENKINS-46307 some slave falling with error of connection lost while still creating
- Closed
- is related to
-
JENKINS-53427 Agent creation failure because of concurrent attempts to schedule a pod
- Reopened