Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Jenkins 2.1.129
-
-
Jenkins 2.130, Remoting 3.23
Description
Jenkins Windows Agent failed to start after upgrade to version 2.1.129: Jenkins is running behind apache reverse proxy on different host that proxy itself. Parameter “tunnel connection through” is set correctly. From the error message we can see that remote agent was trying to connect to reverse proxy host instead of Jenkins master host.
The version 2.1.128 works without issues.
Attachments
Issue Links
- relates to
-
JENKINS-51818 Slave can`t connect via JNLP if Jenkins behind the balancer
-
- Resolved
-
-
JENKINS-52246 Remoting "-tunnel" option is obsolete, redesign needed
-
- Open
-
- links to
See my comment in https://github.com/jenkinsci/remoting/pull/279 . After the review, this issue happens IFF "-tunnel" is set. I believe that "-tunnel" flag should be deprecated and replaced by offering a custom port in TcpAgentListener response headers like it's already done for hosts
So I propose to just disable checks in that case if denami agrees. We could implement a more advanced behavior and checks for tunnel options as a part of JENKINS-52246.