Unable to increase Max number of machines in pool

[gpenunuri]

Having a weird problem. I have a dedicated pool that will not provision more VM's.  It is stuck at 23 even though I have told it to create 35 up-front.  It worked initially and I was able to add a few more after the pool was first created.  It works fine otherwise and i can rebuild existing VM's but jut not able to add more.  There are no errors anywhere that I can see.  It doesn't even try to provision.

Environment ....

Horizon 7.2.0

vSphere 6.5.0

App Vol 2.12.1

[techguy129]

What is the pools naming convention for the computer objects? Did you perhaps ran out of numbers? View will continue to increment computer objects and stop when it runs out. It doesn't like reusing numbers unless you change a setting in the db.

[gpenunuri]

No, there are plenty of numbers.  It is unique to this pool and there are hundreds of names available.  It's weird that it just ignores it and doesn't even log an error anywhere. 

[cjgardne]

Are there any errors in the events tab in Horizon Administrator?

[cjgardne]

I know you said there were no errors that you could see, but I wasn't sure where you were looking exactly. The last event in the events tab was just you changing the setting from 23 to 35?

[HussamRabaya]

please check the below:
1- check the provision is enabled for that pool otherwise it will not create desktop
2- check naming pattern  as restrictive naming pattern i.e (pattern{n:fixed=1}) pools can run out of available view desktop names

please check the below:

1- check the provision is enabled for that pool otherwise it will not create desktop

2- check naming pattern as restrictive naming pattern i.e (pattern{n:fixed=1}) pools can run out of available view desktop names

please check the below:
1- check the provision is enabled for that pool otherwise it will not create desktop
2- check naming pattern  as restrictive naming pattern i.e (pattern{n:fixed=1}) pools can run out of available view desktop names
please check the below:
1- check the provision is enabled for that pool otherwise it will not create desktop
2- check naming pattern  as restrictive naming pattern i.e (pattern{n:fixed=1}) pools can run out of available view desktop names
please check the below:
1- check the provision is enabled for that pool otherwise it will not create desktop
2- check naming pattern  as restrictive naming pattern i.e (pattern{n:fixed=1}) pools can run out of available view desktop names
please check the below:
1- check the provision is enabled for that pool otherwise it will not create desktop
2- check naming pattern  as restrictive naming pattern i.e (pattern{n:fixed=1}) pools can run out of available view desktop names
please check the below:
1- check the provision is enabled for that pool otherwise it will not create desktop
2- check naming pattern  as restrictive naming pattern i.e (pattern{n:fixed=1}) pools can run out of available view desktop names
please check the below:
1- check the provision is enabled for that pool otherwise it will not create desktop
2- check naming pattern  as restrictive naming pattern i.e (pattern{n:fixed=1}) pools can run out of available view desktop names
please check the below:
1- check the provision is enabled for that pool otherwise it will not create desktop
2- check naming pattern  as restrictive naming pattern i.e (pattern{n:fixed=1}) pools can run out of available view desktop names

[mulcas]

Hi gpenunuri,

It is weird you get no error message.

1. Check "events" to see if you could gather extra information.
2. Verify "Enable provisioning" is checked and try unchecking "Stop provisioning on error" from Desktop pool > Edit...
3. Make sure you have enough IP address available from your pool. Probably the DHCP pool is full after deleting old VMs.
4. Resources should be an issue, due to you are not getting an error message, but double-check CPU, Memory and Storage resources.

Cheers,

mulcas

[gpenunuri]

There are no errors logged anywhere in the Horizon console.  I can increase VM's on other pools with no issues just not this specific pool.  I can restart VM's so I know the service account it working.  When you increase the number of VM's in the pool it should start cloning the template but never does.  It just ignores it.  It's so weird.  This just started after upgrading to 7.2. 

[BenFB · Accepted solution]

This could be a ADLDS (ADAM) synchronization issue from the upgrade. Try restarting the environment following Restart order of the View environment to clear ADLDS (ADAM) synchronization in Horizon View (2068381...​.

[gpenunuri]

Thanks for the suggestion Ben.  The reboot of the environment fixed the issue.  Sucks I had to reboot everything.  Hopefully that doesn't happen again.