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

swarm client 3.4 encounters 403 obtaining jnlp while 2.0 connects

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Component/s: swarm-plugin
    • Labels:
      None
    • Environment:
      Jenkkins 2.73.1 LTS, Swarm plugin 3.4, Swarm client 3.4
    • Similar Issues:

      Description

      Hello there! We are trying to upgrade our Swarm stack, but noticing that swarm-client-3.4.jar can't connect: 

       

      SEVERE: Could not obtain CSRF crumb. Response code: 404
      Failing to obtain http://example:8080/computer/nodename/slave-agent.jnlp
      java.io.IOException: Failed to load http://example:8080/computer/nodename/slave-agent.jnlp: 403 Forbidden
      

      However, if I just run swarm-client-2.0-jar-with-dependencies.jar with the same arguments, it connects. So it clearly isn't a master security/auth issue, it's just an issue with the 3.4 swarm client. This is blocking us from upgrading so would be awesome to figure out what's up!

       

        Attachments

          Issue Links

            Activity

            Hide
            mcrooney mcrooney added a comment -

            Probably related to https://issues.jenkins-ci.org/browse/JENKINS-36667 which I filed over a year ago . Maybe we could get a pair of eyes on it Kohsuke Kawaguchi?

            Show
            mcrooney mcrooney added a comment - Probably related to https://issues.jenkins-ci.org/browse/JENKINS-36667  which I filed over a year ago . Maybe we could get a pair of eyes on it Kohsuke Kawaguchi ?
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

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

            Show
            oleg_nenashev Oleg Nenashev added a comment - KK does not maintain this plugin anymore. Moving to unassigned to set the expectation
            Hide
            basil Basil Crow added a comment -

            This looks like a duplicate of JENKINS-25421. The workaround is to enable CSRF on the Jenkins master.

            Show
            basil Basil Crow added a comment - This looks like a duplicate of JENKINS-25421 . The workaround is to enable CSRF on the Jenkins master.
            Hide
            basil Basil Crow added a comment - - edited

            Is this still a bug on recent versions of Jenkins core and Swarm client? I just tried connecting to a Jenkins master (2.150.1) with Swarm client 3.16 both with and without CSRF enabled on the Jenkins master, and things worked just fine.

            Show
            basil Basil Crow added a comment - - edited Is this still a bug on recent versions of Jenkins core and Swarm client? I just tried connecting to a Jenkins master (2.150.1) with Swarm client 3.16 both with and without CSRF enabled on the Jenkins master, and things worked just fine.

              People

              • Assignee:
                Unassigned
                Reporter:
                mcrooney mcrooney
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: