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

Option "Delay between launch and boot complete" doesn't work

XMLWordPrintable

      Wakeup with "Force VM launch" and "Wait for VMTools" switches doesn't do any delay from "Delay between launch and boot complete" option.

      [rusbuilder-vTest] Starting Virtual Machine...
      [rusbuilder-vTest] Reverting to snapshot:Clean
      [rusbuilder-vTest] Powering on VM
      [rusbuilder-vTest] Waiting for VMTools
      ....
      NLP agent connected from /10.73.2.118
      <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.36
      Dies ist ein Windows-Slave
      Slave successfully connected and online
      [rusbuilder-vTest] VM Tools are running
      [rusbuilder-vTest] Finished wait for VMTools
      [rusbuilder-vTest] Running disconnect procedure...
      [rusbuilder-vTest] Shutting down Virtual Machine...
      Connection terminated
      [rusbuilder-vTest] Attempting a graceful shutdown

        1. settings.png
          settings.png
          36 kB

          [JENKINS-23212] Option "Delay between launch and boot complete" doesn't work

          Jason Swager added a comment -

          I believe that this expected. Although Jenkins is starting the VM (power on), the VM is starting the slave agent on its own. It could be using the Windows Service, Task Scheduler or something else. Your config screen confirms that the slave agent is being started via JNLP.

          The log is showing that the JNLP is connecting (from the VM side) before the timeouts have ended on the Jenkins side. This is fine.

          The rapid disconnect is probably occurring due to the your idle disconnect timer. You have it set to 1 minute.

          Jason Swager added a comment - I believe that this expected. Although Jenkins is starting the VM (power on), the VM is starting the slave agent on its own. It could be using the Windows Service, Task Scheduler or something else. Your config screen confirms that the slave agent is being started via JNLP. The log is showing that the JNLP is connecting (from the VM side) before the timeouts have ended on the Jenkins side. This is fine. The rapid disconnect is probably occurring due to the your idle disconnect timer. You have it set to 1 minute.

          Jason Swager added a comment -

          This issue will be closed shortly. This appears to be expected behavior.

          Jason Swager added a comment - This issue will be closed shortly. This appears to be expected behavior.

          Alexey Larsky added a comment -

          If you sure

          Alexey Larsky added a comment - If you sure

          Jason Swager added a comment -

          Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect.

          Jason Swager added a comment - Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect.

          Jason Swager added a comment -

          Expected behavior

          Jason Swager added a comment - Expected behavior

            Unassigned Unassigned
            alexey_larsky Alexey Larsky
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: