| Hi pjdarton thank you for replying. Yes, when I wrote error I refered to the warning printed on the post above. After creating the issue I realised that having the value 2147483647 is just cosmetic. We are relying on this plugin for creating and destroying jenkins agents on demand. This issue keeps happening with newer versions of the plugin so we are running a job recurrently in our Jenkins instance to avoid this issue. We didn't experience issues of memory. We had issues of VMs with duplicated names but I am not sure it was related with this workaround. We developed a small script that would destroy the virtual machines on vmware that weren't present in Jenkins, after all these are linked clones and were re-created again. Currently we are running Jenkins version: 2.150.3
vsphere-cloud plugin: 2.21 This is a piece of the log where it should create a new jenkins agent (the last one since we set up a hard limit of 50 agents) but it didn't create it
Jan 10, 2020 3:11:32 PM INFO org.jenkinsci.plugins.vSphereCloud provision
provision(xcode-10.1,20): Provisioning 0 new =[]
Jan 10, 2020 3:11:32 PM INFO org.jenkinsci.plugins.vSphereCloud calculateMaxAdditionalSlavesPermitted
There are 49 VMs in this cloud. The instance cap for the cloud is 50, so we have room for more
Jan 10, 2020 3:11:32 PM INFO org.jenkinsci.plugins.vSphereCloud provision
provision(xcode-11.1,6): 0 existing slaves (=0 executors), templates available are [Template[prefix=sod-xxx-01, provisioned=[sod-xxx-011, sod-xxx-0110, sod-xxx-012, sod-xxx-013, sod-xxx-014, sod-xxx-015, sod-xxx-016, sod-xxx-017, sod-xxx-018, sod-xxx-019], planned=[], unwanted={}, max=10, fullness=100.000%]]
That piece of log just keeps repeating over and over. After running the job with the mentioned workaround it starts creating agents again. Regards, |
