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

vSphere plugin not respecting or saving per slave instance Cap

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • vsphere-cloud-plugin
    • None
    • Jenkins 2.14
      vSphere Plugin 2.14

      Even though the vSphere configuration for dynamic slaves has a field for setting a per slave instance cap, that cap is not honored and does not seem to actually be saved in the config.xml file.

      In my slave definition, I set the slave instance cap to 2. But in the Jenkins log, I was finding this:
      There are 0 number of VMs with the prefix UbuntuSlave-1. The instance cap for VMs with that prefix is: 2147483647

      When I looked at the definition in the config.xml for the cloud, you can see that there is no per instance cap in the config.

      My instance cap globally is 2 slaves that should be started. That is not honored either. It seems to limit the number of slaves actually used for builds, but then it seems to actually generate more slaves that that. I will attach the xml snippet from config, and a screenshot of what happened for the number of slaves generated.

            Unassigned Unassigned
            gregcovertsmith Greg Smith
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: