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

Upgrading throttle-concurrent-builts-plguin från 1.9 -> 2.0 disables ability for nodes to connect in Jenkins LTS

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Environment:
    • Similar Issues:

      Description

      After upgrading throttle-concurrent-builts-plguin från 1.9 > 2.0, the master will no longer connect to the nodes for no apparent reason. Downgrading the plugin restores normal operation and the master will again connect to the nodes.

       

        Attachments

          Activity

          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Please provide Jenkins system and agent logs. Without it it is impossible to say what may go wrong. There is no direct relation between TCB and agent connection

          Show
          oleg_nenashev Oleg Nenashev added a comment - Please provide Jenkins system and agent logs. Without it it is impossible to say what may go wrong. There is no direct relation between TCB and agent connection
          Hide
          bjro bjorn rohlen added a comment -

          As part of the Swedish government, we are not allowed to post logs in such manner, so I am afraid we cannot provide more information than the above. I checked the startup logs and could not find anything which stood out, so we will just stick to 1.9. 

          Thanks!

           

          Show
          bjro bjorn rohlen added a comment - As part of the Swedish government, we are not allowed to post logs in such manner, so I am afraid we cannot provide more information than the above. I checked the startup logs and could not find anything which stood out, so we will just stick to 1.9.  Thanks!  
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          And what about agent logs? I mean the ones being printed on the agent side when Remoting starts, not the ones available in UI.

          Show
          oleg_nenashev Oleg Nenashev added a comment - And what about agent logs? I mean the ones being printed on the agent side when Remoting starts, not the ones available in UI.
          Hide
          bjro bjorn rohlen added a comment -

          I put the alarm at 04:00 this morning and upgraded from 1.9 > 2.0 and checked the swarm3.3-logs, they disconnect when the master restarts, then just sit at "Discovering", with no further output. I waited 15 minutes and downgraded to 1.9, and restarted the agents, it got right back up.

          Show
          bjro bjorn rohlen added a comment - I put the alarm at 04:00 this morning and upgraded from 1.9 > 2.0 and checked the swarm3.3-logs, they disconnect when the master restarts, then just sit at "Discovering", with no further output. I waited 15 minutes and downgraded to 1.9, and restarted the agents, it got right back up.
          Hide
          bjro bjorn rohlen added a comment -

          ... when the master is down, they try to reconnect every 10s (as set in ENV), which generates "buzz" in the logfiles, this just... freezes. 

          Show
          bjro bjorn rohlen added a comment - ... when the master is down, they try to reconnect every 10s (as set in ENV), which generates "buzz" in the logfiles, this just... freezes. 
          Hide
          bjro bjorn rohlen added a comment -

          Safe to say, I tried restarting the agents when 2.0 was installed to see if they would connect, but they just got stuck at "Discovering master" (which is set by IP, no discovering necessary).

          Show
          bjro bjorn rohlen added a comment - Safe to say, I tried restarting the agents when 2.0 was installed to see if they would connect, but they just got stuck at "Discovering master" (which is set by IP, no discovering necessary).
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption.

          If anybody is interested, let me know

          Show
          oleg_nenashev Oleg Nenashev added a comment - Unfortunately I was unable to find time to work on plugin over last year. I decided to step down as maintainer and to mark the plugin for adoption. If anybody is interested, let me know

            People

            • Assignee:
              Unassigned
              Reporter:
              bjro bjorn rohlen
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: