My Environment:
vCenter: 6.5U1 (build 7515524)
Horizon: 7.5.0 (I have 5 connection server 3 of then in domain domain1.com and two other in domain2.com)
I have a test server with ESXi 6.5 and local flash datastore (SSD).
Doing all by this instruction (I also read all Horizon documentation about instant clone) - VMware Horizon View 7: Instant Clone Desktop Pool [Part 8] - VirtuallyBoring
After finish pool creation master, I have this error:
in log files I only find this:
2018-08-06T13:27:06.361+03:00 DEBUG (1F58-09A8) <DesktopControlLdap> [DesktopTracker] Update pool from LDAP notification: cn=vdi_test04,ou=server groups,dc=vdi,dc=vmware,dc=int
2018-08-06T13:27:06.361+03:00 DEBUG (1F58-09A8) <DesktopControlLdap> [InformationBase] PoolInformation[cn=vdi_test04,ou=server groups,dc=vdi,dc=vmware,dc=int]::pae-VmProvEnabled is now false
2018-08-06T13:27:06.361+03:00 DEBUG (1F58-09A8) <DesktopControlLdap> [InformationBase] PoolInformation[cn=vdi_test04,ou=server groups,dc=vdi,dc=vmware,dc=int]::pae-VmProvError is now Initial publish failed: Unknown error, fault not set
2018-08-06T13:27:06.361+03:00 DEBUG (1F58-09A8) <DesktopControlLdap> [InformationBase] PoolInformation[cn=vdi_test04,ou=server groups,dc=vdi,dc=vmware,dc=int]::pae-VmProvErrorTime is now 1533551195
2018-08-06T13:27:06.361+03:00 DEBUG (1F58-09A8) <DesktopControlLdap> [InformationBase] PoolInformation[cn=vdi_test04,ou=server groups,dc=vdi,dc=vmware,dc=int]::pae-PendingParentImageState is now FAILED
2018-08-06T13:27:06.361+03:00 DEBUG (1F58-09A8) <DesktopControlLdap> [InformationBase] PoolInformation[cn=vdi_test04,ou=server groups,dc=vdi,dc=vmware,dc=int]::pae-NgvcPoolPendingOperation is now null
2018-08-06T13:27:06.361+03:00 DEBUG (1F58-09A8) <DesktopControlLdap> [InformationBase] PoolInformation[cn=vdi_test04,ou=server groups,dc=vdi,dc=vmware,dc=int]::pae-SVIVmOperationSchedule is now null
In Horizon 7.3.2 release notes found this:
Instant-clone operations fail with Horizon 7 version 7.3.1 or version 7.3 while connecting to vCenter Server in some situations. This failure can have significant consequences in production and is now handled gracefully in Horizon 7 version 7.3.2.
Upgraded from 7.3.1 to 7.5.0 but this doesn't helped.
Googl doesn't helped at all.... 😕
Will be grateful for any clues where to look the issue.