Horizon v7.50 with VCSA v6.7 and ESXi v6.5U2

[jedijeff]

Hi. We are having some issues provisioning instant clones using Horizon v7.50 with vCenter v6.7, yet our hypervisors are still ESXi v6.5U2.

All hosts show these errors in a connection server log.

2018-06-12T00:23:27.448-04:00 WARN  (1008-1878) <CacheRefreshThread-https://blahblah:443/sdk> [ObjectStore] Host: host-26 not available for provisioning. ConnectionState=connected, PowerState=poweredOn, MaintenanceMode=false, AdminRequestedMaintenance=0, MarkedAsFailed=false, Host Version: 6.5.0, Host API Version: 6.5

Creating a new Instant Clone pool fails with this

No full links for internal VMs found

I am just not sure what is the cause or effect? The hosts are healthy, and all have access to the proper datastores, etc. Can anyone point me in a direction? Is there an issue with VCSA v6.7 and trying to use the new Instant Clone API yet the hypervisors are still v6.5U2? Thanks,,,

[sjesse]

I'm not sure that is supported, I'd check with vmware, for horizon I think you need vcenter and the hosts the same version. The problem is 6.7 uses different api calls for instant clones than 6.5, and I wonder if sending the calls to a 6.7 vcenter is not working for horizon.

[LarryBlanco2 · Accepted solution]

you need at least 1x 6.7 host in the cluster for IC to work properly.   It's in the documentation.  I can't find it now but that's the issue.

LB

[jedijeff]

Hi. That does appear to be the issue. We went ahead and upgraded all hosts to v6.7 anyway. If you find it in the documetation, I certainly would like to know where. We didnt see anything in the release notes. Thanks,,,

[LarryBlanco2]

Here you go:

Upgrade Instant-Clone Desktop Pools

Step 7:

1. Perform a push-image operation for each instant-clone desktop pool that uses the new snapshot.Only the hosts that are upgraded to vSphere 6.7 ESXi are used for provisioning. The instant clones created during the push-image operation might be migrated to other hosts that are not yet on vSphere 6.7.

Larry B.