VMware Horizon Community
tyler1985
Contributor
Contributor
‎05-10-2017 03:57 AM

Ufter upgrade to Horizon 7.1 can't provision new full-clone machines

We have 3-node cluster VDI on ESXi 6.5 with all-flash VSAN. All work fine, but about 2 weeks ago after upgrade to horizon 7.1 we see error during provisioning in full-clone desktop pool: "Error during provisioning: No suitable datastores." But datastore have 2,2 Tb free space... Can't find any information why this error happens...

Please help me to understand why this error happens...

There is datastore property in log file wich I can't understand - OutOfFreeSpaceForHWMem

there is log from view connection server:

2017-04-24T15:06:19.226+03:00 DEBUG (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [PendingOperation] $Prof: Operation=AcquireCloneLock@FullCloneCreation, Object=VmPath:/kodeks/vm/testpool1/testpool-001, Time=0 ms

2017-04-24T15:06:19.226+03:00 DEBUG (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [DatastoreSelectorDSCache] Refreshing DSCache: initialized=true vmsProvisioned=0 forceRefresh=false

2017-04-24T15:06:19.228+03:00 DEBUG (0910-1980) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] SecurityManager::Decrypt

2017-04-24T15:06:19.228+03:00 DEBUG (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [DatastoreSelectorDSCache] Done refreshing DSCache

2017-04-24T15:06:19.228+03:00 DEBUG (0910-1980) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Tag: {SSO-AES:1}

2017-04-24T15:06:19.228+03:00 DEBUG (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [DatastoreSelectorCached25] Full clone datastore details for datastore: path = /kodeks/host/VDI cluster/vsanDatastore, capacity = 4471.258689880371 GB, free space = 2270.626773422584 GB

2017-04-24T15:06:19.228+03:00 DEBUG (0910-1980) <MessageFrameWorkDispatch> [ws_java_bridgeDLL] Keyspec: SECURITYMGRSSO#1

2017-04-24T15:06:19.229+03:00 DEBUG (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [DatastoreSelectorCached25] Datastore: /kodeks/host/VDI cluster/vsanDatastore not being considered for clone selection. OutOfFreeSpaceForHWMem Details: DSProperties [isAccessible=true, dsMoid=datastore-34, capacityGB=4471.258689880371, freeSpaceGB=2270.626773422584, consecutiveSelectionPenaltyGB=0.0, totalHwMemOfPoweredOffVmsGB=4263.5927734375, overcommittedUsageGB=9782.294921875]

2017-04-24T15:06:19.229+03:00 WARN  (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [DatastoreSelectorCached25] No suitable datastores found for provisioning a full clone: DS: /kodeks/host/VDI cluster/vsanDatastore : FreeSpaceDeficient,

2017-04-24T15:06:19.230+03:00 ERROR (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [PendingOperation] Pool control for desktop testpool1 is unable to create the new VM testpool-001 - No suitable datastores.

2017-04-24T15:06:19.231+03:00 INFO  (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [VirtualCenterDriver] VirtualCenter control for https://vdi-vcenter.work.kodeks.ru:443/sdk is suspending operations - VM operation failed: com.vmware.vdi.vcsupport25.DatastoresReservedException25: No suitable datastores.

2017-04-24T15:06:19.231+03:00 INFO  (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [Audit] VC_DISABLED:VC:cn=8b284209-ad60-44a9-8710-b38523a8d8f1,ou=virtualcenter,ou=properties,dc=vdi,dc=vmware,dc=int;REASON:VM operation failed: com.vmware.vdi.vcsupport25.DatastoresReservedException25: No suitable datastores.;

2017-04-24T15:06:19.231+03:00 DEBUG (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [EventLogger] Info_Event:[BROKER_VC_DISABLED] "vCenter at address https://vdi-vcenter.work.kodeks.ru:443/sdk has been temporarily disabled": VCId=8b284209-ad60-44a9-8710-b38523a8d8f1, Node=vdi-connection1.work.kodeks.ru, Severity=INFO, Time=Mon Apr 24 15:06:19 AST 2017, VCAddress=https://vdi-vcenter.work.kodeks.ru:443/sdk, Module=Broker, Source=com.vmware.vdi.desktopcontroller.VirtualCenterDriver, Acknowledged=true

2017-04-24T15:06:19.233+03:00 ERROR (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [PoolInformation] Pool control for desktop testpool1 is disabling provisioning due to a clone error - No suitable datastores.

2017-04-24T15:06:19.233+03:00 DEBUG (0910-2358) <PendingOperation-/kodeks/vm/testpool1/testpool-001-Cloning> [PoolInformation] Exception for clone error: com.vmware.vdi.desktoptracker.PoolInformation.onCloneError(SourceFile:1853)

com.vmware.vdi.vcsupport25.DatastoresReservedException25: No suitable datastores.

Reply
0 Kudos
1 Reply
jonathanjabez
Hot Shot
Hot Shot
‎02-27-2020 08:37 PM

Hi Tyler,

I am responding to an old community discussion. First, you make sure you have chosen the option  in Pool settings "Use vSAN" for datastore and you have selected the vSAN datastore.

Try to adjust the overcommit level or the number of virtual machines in the Linked-Clone Pool.

To adjust the overcommit level or the number of virtual machines in the Linked-Clone Pool:

  1. Log in to the View Administrator page.
  2. Navigate to Inventory > select the pool name and click Edit.
  3. Navigate to Pool Sizing > Provisioning Settings tab adjust the number of virtual machines in Max number of desktops and click OK.

    Note: Calculate your Max number of desktops depending on your environment, see Calculating Datastore Selection for Linked-Clone Desktops in Horizon View 5.2 or Later Releases (204...
Reply
0 Kudos