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

Slaves not discovering when Maven is not enabled on the master

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • swarm-plugin
    • OS - Centos 6.5 64 bit
      Jenkins - 1.614
      Swarm - 1.24
      Slave - swarm-client-1.24-jar-with-dependencies.jar
      Java (Master & Slave) - OpenJDK Runtime Environment (build 1.8.0_45-b13)

      Hi,

      This is not a blocker. I was trying the slave auto discovery in the above mentioned scenario. Without having the Maven installed on the master when I tried:

      java -jar swarm-client-1.24-jar-with-dependencies.jar -autoDiscoveryAddress 192.168.55.22 -name Slave1
      

      I get the following error message:

      Jenkins master at '/192.168.55.22' doesn't have a valid Jenkins URL configuration set. Please go to <jenkins url>/configure and set a valid URL.
      No nearby Jenkins supports swarming
      Retrying in 10 seconds
      

      even though the url is set correctly in the master.

      Please let me know if you need more information in this regard.

      Cheers

          [JENKINS-28518] Slaves not discovering when Maven is not enabled on the master

          That is quite weird. I would have to take a look at this case.

          Peter Jönsson added a comment - That is quite weird. I would have to take a look at this case.

          Jörg Ziegler added a comment -

          Seeing the same error message with 1.642.2 running on Linux, using swarm-client-2.0-jar-with-dependencies.jar.
          It seems to be a missing initialization: The jenkins-url is correctly populated after jenkins installations but apparently not returned to the swarm client. Going to /configure and manually saving the configuration once fixes the problem.

          It's not a blocker since there's an easy workaround, however since we're trying to auto-setup jenkins from docker, it's a bummer that we can't fully automate it. Hoping that with this info it'll be an easy fix?

          Jörg Ziegler added a comment - Seeing the same error message with 1.642.2 running on Linux, using swarm-client-2.0-jar-with-dependencies.jar. It seems to be a missing initialization: The jenkins-url is correctly populated after jenkins installations but apparently not returned to the swarm client. Going to /configure and manually saving the configuration once fixes the problem. It's not a blocker since there's an easy workaround, however since we're trying to auto-setup jenkins from docker, it's a bummer that we can't fully automate it. Hoping that with this info it'll be an easy fix?

          Joshua Knarr added a comment -

          Bumping for me. I am using puppet to install jenkins and was pulling my hair out. Loading the configuration and clicking "save" once fixes this.

          Joshua Knarr added a comment - Bumping for me. I am using puppet to install jenkins and was pulling my hair out. Loading the configuration and clicking "save" once fixes this.

          Abdallah Atie added a comment -

          I am seeing the same behaviour, just going to the configure page and resaving it solves the issue.

          The problem is that I am using and ansible playbook to deploy a master and a number of slaves using the swarm plugin and that makes the playbook fail systematically the first time.

          A-

          Abdallah Atie added a comment - I am seeing the same behaviour, just going to the configure page and resaving it solves the issue. The problem is that I am using and ansible playbook to deploy a master and a number of slaves using the swarm plugin and that makes the playbook fail systematically the first time. A-

          Oleg Nenashev added a comment -

          KK does not maintain this plugin anymore. Moving to unassigned to set the expectation

          Oleg Nenashev added a comment - KK does not maintain this plugin anymore. Moving to unassigned to set the expectation

          Basil Crow added a comment -

          As of Swarm 3.18, the UDP broadcast auto-discovery service has been removed. So this code no longer exists and this should no longer be an issue. If this problem occurs again, please ensure you are running the latest version of the Swarm plugin and Swarm client, referring to the documentation on how to configure authentication and authorization. If the problem persists, please open a new issue with detailed steps to reproduce.

          Basil Crow added a comment - As of Swarm 3.18 , the UDP broadcast auto-discovery service has been removed. So this code no longer exists and this should no longer be an issue. If this problem occurs again, please ensure you are running the latest version of the Swarm plugin and Swarm client, referring to the documentation on how to configure authentication and authorization. If the problem persists, please open a new issue with detailed steps to reproduce.

            Unassigned Unassigned
            ssrini Srini Sundaram
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: