Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-63607

remoting 4.5 in jenkins 2.235.5 is detected as too old...

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      we are using a lot of agents with swarm plugin.

      all agents always download the agent, and then connect to the server.

      installing versions node monitor 2.1 caused all the nodes to go OFFLINE since the version node plugin reports remoting 4.5 ON CLIENT SIDE as too old...

       

      simply put - when a node reports it has remoting version 4.5 and the master has remoting version 4.3 -> the node is taken offline.

        Attachments

          Activity

          Hide
          amidar Amit Dar added a comment - - edited

          I don't understand why the jenkins controller should/would be upgraded before the agent. we are upgrading the plugins all the time to keep all the system up to date as much as possible.

          since we are using swarm plugin massively, we keep it always up to date with the latest compatible version to the controller.

          the last upgrade was a disaster to us since all the agent went offline immediately after the update...

          anyway - thanks for the solution

          Show
          amidar Amit Dar added a comment - - edited I don't understand why the jenkins controller should/would be upgraded before the agent. we are upgrading the plugins all the time to keep all the system up to date as much as possible. since we are using swarm plugin massively, we keep it always up to date with the latest compatible version to the controller. the last upgrade was a disaster to us since all the agent went offline immediately after the update... anyway - thanks for the solution
          Hide
          markewaite Mark Waite added a comment -

          Yes, I'm suggesting a work around. I agree that an agent running a newer version of remoting should be able to connect to an older remoting version on the Jenkins controller. I suspect that is an uncommon scenario, since most of the time the controller is upgraded before the agents are upgraded.

          Show
          markewaite Mark Waite added a comment - Yes, I'm suggesting a work around. I agree that an agent running a newer version of remoting should be able to connect to an older remoting version on the Jenkins controller. I suspect that is an uncommon scenario, since most of the time the controller is upgraded before the agents are upgraded.
          Hide
          amidar Amit Dar added a comment -

          Hi Mark Waite,

           

          thanks for the quick response!

          I just want to make sure I fully understand - you are suggesting a "workaround" rather than a solution.

          what I'm trying to say is that the remoting version should "behave" like the java version. it should offer at least some sort of validation mechanism and not provide a simple "check/don't check" mechanism for the specific remoting version.

           

          shouldn't an agent with remoting version 4.5 be able to connect to a master with remoting version 4.3? I don't see a reason why it shouldn't (unless there are some breaking api changes, which means the agent should be versioned 5.something....

           

          don't you agree?

          Show
          amidar Amit Dar added a comment - Hi Mark Waite ,   thanks for the quick response! I just want to make sure I fully understand - you are suggesting a "workaround" rather than a solution. what I'm trying to say is that the remoting version should "behave" like the java version. it should offer at least some sort of validation mechanism and not provide a simple "check/don't check" mechanism for the specific remoting version.   shouldn't an agent with remoting version 4.5 be able to connect to a master with remoting version 4.3? I don't see a reason why it shouldn't (unless there are some breaking api changes, which means the agent should be versioned 5.something....   don't you agree?
          Hide
          markewaite Mark Waite added a comment -

          The versioncolumn plugin can be configured to not mark the agent offline when the remoting version does not match the version on the Jenkins controller.

          See JENKINS-63557 that announces the release of swarm client 3.23 (for Jenkins 2.249.1). You may need to remain with swarm plugin 3.22 on Jenkins 2.235.x

          Show
          markewaite Mark Waite added a comment - The versioncolumn plugin can be configured to not mark the agent offline when the remoting version does not match the version on the Jenkins controller. See JENKINS-63557 that announces the release of swarm client 3.23 (for Jenkins 2.249.1). You may need to remain with swarm plugin 3.22 on Jenkins 2.235.x

            People

            Assignee:
            batmat Baptiste Mathus
            Reporter:
            amidar Amit Dar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: