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

vSphere Nodes are never started when in demand

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • vsphere-cloud-plugin
    • None
    • Jenkins 2.7.4
      vsphere-cloud 2.14 + yavijava 6.0.04

      I have started to experiment with vSphere Nodes, both vSphereCloudSlave and vSphereCloudProvisionedSlave.

      I use a retentionStrategy of Demand and have inDemandDelay 1 and idleDelay 30.

      vSphere-cloud-plugin correctly shuts the vm down after 30 min of idle, but when there are jobs in the queue waiting for executors longer that one minute, it never starts the vm up.

      Btw, there are no launchSlaveAgent link on the node page, but using the url directly starts the VM correctly.

            Unassigned Unassigned
            glance Anton Lundin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: