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

VirtualBox windows VM Build Agent cannot connect to master with agent/master access control disabled

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Component/s: core, virtualbox-plugin
    • Environment:
      Jenkins version 2.51 running on debian jessie. The VM is running Windows Server 2008 R2 SP1 64-bit via VirtualBox. Both are running the latest Java.
    • Similar Issues:

      Description

      I've looked through many seemingly-related issues regarding a slave not being able to connect to a master. However, after hours of attempting different fixes (disabling security, attemtping to pass -jnlpCredentials of an existing jenkins user); nothing seems to work but downgrading to <2.7. The slave reports a 403 Forbidden error when attempting to access build-agent.jnlp

      The following is what appears on the master log:

      INFO: Accepted connection #8 from /10.128.218.31:33521
      Mar 22, 2017 1:48:29 PM jenkins.slaves.DefaultJnlpSlaveReceiver afterProperties
      WARNING: Rejecting connection to win2k8 from /10.128.218.32:33521 as a JNLP agent as the launcher class hudson.plugins.virtualbox.VirtualBoxComputerLauncher does not extend JNLPLauncher or does not implement DelegatingComputerLauncher with a delegation chain leading to a JNLPLauncher. Set system property jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification=true to allowconnections until the plugin has been fixed.
      Mar 22, 2017 1:49:22 PM hudson.slaves.RetentionStrategy$Demand check
      INFO: Launching computer win2k8 as it has been in demand for 13 hr

       

        Attachments

          Issue Links

            Activity

            Hide
            kslice Kevin McHale added a comment -

            It was unclear where the system property jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification is set. Once I realized it is not set on the slave, but rather the master, I've updated /etc/default/jenkins to reflect the additional argument and it appears to have fixed the problem for now.

            Show
            kslice Kevin McHale added a comment - It was unclear where the system property jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification is set. Once I realized it is not set on the slave, but rather the master, I've updated /etc/default/jenkins to reflect the additional argument and it appears to have fixed the problem for now.

              People

              • Assignee:
                godin godin
                Reporter:
                kslice Kevin McHale
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: