VMware Horizon Community
stgepopp
Hot Shot
Hot Shot

UFA error: fail in disk format operation

Hi experts,

just installed a vSAN 6.7 Cluster with four hosts and some Horizon View Components on it: Connection Server 7.5, Composer 7.5 with external MS SQL 2017 DB and some more.

Problem:

Linked Clone Pools are not succesfully provisioned

Connection Server:

View Composer DiskFault: Disk customization failed due to an internal error

Composer Server:

2018-07-18 15:42:41,449 | UFA main thread 3 | FATAL | CommonLib.UfaSubsystem.UfaWorkItem - UFA error: fail in disk format operation.

2018-07-18 15:42:41,449 | UFA main thread 3 | INFO  | CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem - UFA error: fail to finish init disk operation for disk: datastore: [vsanDatastore] cb434f5b-c6b6-d928-f3c1-b88303450b6c/LC-TEST-021-internal.vmdk, host: esxi.fqdn, port: 902.

2018-07-18 15:42:41,449 | UFA main thread 3 | DEBUG | CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem - UFA: Making a call to UFA's CloseVolumesAndDisks

2018-07-18 15:42:41,449 | UFA main thread 4 | DEBUG | CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem - UFA: formatting the disk: datastore: [vsanDatastore] cb434f5b-5a9a-e487-0272-d06726d20850/LC-TEST-011-internal.vmdk, host: esxi.fqdn, port: 902.

2018-07-18 15:42:41,449 | UFA main thread 4 | FATAL | CommonLib.UfaSubsystem.UfaWorkItem - UFA error: fail in disk format operation.

2018-07-18 15:42:41,449 | UFA main thread 4 | INFO  | CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem - UFA error: fail to finish init disk operation for disk: datastore: [vsanDatastore] cb434f5b-5a9a-e487-0272-d06726d20850/LC-TEST-011-internal.vmdk, host: esxi.fqdn, port: 902.

2018-07-18 15:42:41,449 | UFA main thread 4 | DEBUG | CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem - UFA: Making a call to UFA's CloseVolumesAndDisks

2018-07-18 15:42:41,464 | UFA main thread 3 | DEBUG | CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem - UFA: Returned from UFA's CloseVolumesAndDisks method

2018-07-18 15:42:41,464 | UFA main thread 4 | DEBUG | CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem - UFA: Returned from UFA's CloseVolumesAndDisks method

2018-07-18 15:42:41,464 | UFA main thread 3 | FATAL | CommonLib.UfaSubsystem.UfaSubsystem - UFA error: failure in operation with soap fault: SysimageFaultVstor2NotRunningFault

VMware.Sim.CommonLib.Exception.SimUfaSubsystemException: UFA soap fault error. ---> System.Web.Services.Protocols.SoapException: sysimage.fault.Vstor2NotRunning

   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)

   at Sysimage.SysimageService.Format(ManagedObjectReference _this, String fsType, String volumeLabel, Int32 allocationSizeInBytes, Boolean allocationSizeInBytesSpecified, Boolean compress, Boolean compressSpecified, Boolean quickFormat, Boolean quickFormatSpecified)

   at VMware.Sim.CommonLib.UfaSubsystem.UfaWorkItem.Format(ManagedObjectReference volume)

   at VMware.Sim.CommonLib.UfaSubsystem.InitializeDiskUfaWorkItem.DoWork()

   at VMware.Sim.CommonLib.UfaSubsystem.UfaWorkItem.Run()

(Changed the host names)

Found nothing really helpful with searching the internet.

My guess is problems with authentication to the esxi hosts, but not sure

Did anybody come accross this failure?

Thanks

Tags (4)
Reply
0 Kudos
2 Replies
sumann7
Contributor
Contributor

Hi stgepopp,

Please validate the below KB If everything seems to be fine then, please reinstall the composer to fix the issue.

KB1024566

From the log you provided :

2018-07-18 15:42:41,464 | UFA main thread 3 | FATAL | CommonLib.UfaSubsystem.UfaSubsystem - UFA error: failure in operation with soap fault: SysimageFaultVstor2NotRunningFault

I think this driver is not installed or is corrupted.

Regards,

Reply
0 Kudos
MrCheesecake
Enthusiast
Enthusiast

I've seen a similar issue where the Composer server was separated from the ESX hosts with a firewall and TCP-902 was not allowed from the Composer server.  In that case, View was reporting "Selected parent VM is not accessible" but a lot of the composer log entries look similar.

Reply
0 Kudos