timja / jenkins-gh-issues-poc-06-18

0 stars 0 forks source link

[JENKINS-68739] Jenkins 2.354 remoting version mismatch #6065

Closed timja closed 2 years ago

timja commented 2 years ago

TC

  1. Install Jenkins 3.354
  2. Attach client with remoting 4.13

AR: Slave marked as offline due to old agent version

ER: Slave woks with out marks

 

According to change log Jenkins 2.354 depends on remoting 4.13, but provides  3025.vf64a_a_3da_6b_55


Originally reported by bulanovk, imported from: Jenkins 2.354 remoting version mismatch
  • assignee: jthompson
  • status: Closed
  • priority: Critical
  • resolution: Not A Defect
  • resolved: 2022-06-10T16:29:19+00:00
  • imported: 2022/01/10
timja commented 2 years ago

markewaite:

Thanks for the report! Jenkins 2.354 includes remoting version 3025.vf64a_a_3da_6b_55. By default, remoting 4.13 agents are allowed to connect to the Jenkins controller.

If you have the version node monitors plugin installed and configured to disconnect agents with older remoting versions, then you'll need to either upgrade the remoting version of the inbound agent, relax the restriction on the remoting version in the version node monitors plugin configuration, or switch from an inbound agent to an ssh agent (since ssh agents automatically upgrade their remoting version).

The official Jenkins 2.354 changelog did not mention the remoting upgrade.  It should mention that upgrade, since we've mentioned it in previous releases like Jenkins 2.338 and Jenkins 2.334. Thanks again for reporting it.

https://github.com/jenkins-infra/jenkins.io/pull/5218 submitted to add the mention to the change.