search

jenkinsci / azure-slave-plugin

18 stars 41 forks source link

cannot start the existing vms on vm limit reach #40

Open pesetskyps opened 8 years ago

pesetskyps commented 8 years ago

If I provisioned the slaves and shutdown them on retention time I face the situation that when limit is reached existing vms didn't not start with error in logs:

Azure Cloud: provision: template jenk-win-slavehas validation errors , cannot provision slaves with this configuration [The current number of virtual machines in this Azure subscription is 40, which is more than or equal to the default value 40 
.Consider increasing Max Virtual Machines Limit value or delete existing virtual machines from your subscription.

That's because this validation happens and prevent further check. This should be changed to check after existing vms check.

pesetskyps commented 8 years ago

Is there any ideas how to fix this? Thanks in advance

arodus commented 8 years ago

I managed to fix this problem. Was a little bit tricky and had to rewrite some code. Now I have to fix the integrated tests. Since I'm not that familiar with Jenkins and java any help is appreciated.

arroyc commented 7 years ago

@pesetskyps ... Can you please try with the latest bits from ARM-dev branch?

pesetskyps commented 7 years ago

@arroyc thank you for the time to fix. Currently I have no jenkins to test on as my one is production so can't use dev branch plugin version(

arroyc commented 7 years ago

@pesetskyps ...we have released Azure VM agent plugin .. it's no more a dev branch ... Can you please try the new one?