Unable to store deployment tasks in the persistant location

Can you restart the vSphere web-client service and re-register (unregister and then register) the scaleio vsphere web plugin and then restart the deployment?

Hi,

In order to  better analyze the problem and check if the root cause is a known bug that was found in 1.32.4 and fixed for 1.32.5, we need the Virgo logs (see paths below)

Also any other info you can supply will help, such as:

- Which VC OS and exact version (6.0 | 6.0u1/u2) are you using?

- Which ESX version (5.5u1/2/3 | 6.0u1/2)?

- ESX disk size and type, are there HDD/SSD used in the deployment

**Paths per VC version and OS **

VC 5.5

Windows:

Virgo logs: C:\ProgramData\VMware\vSphere Web Client\serviceability\logs

Plugin logs and other files: C:\Windows\System32\config\systemprofile\AppData\Roaming\VMware\scaleio

Plugin location C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity

Linux:

Virgo logs: /var/log/vmware/vsphere-client/

Plugin logs and other files: /opt/.vmware/scaleio

Plugin location /var/lib/vmware/vsphere-client/vc-packages/vsphere-client-serenity/

VC 6.0

Windows:

Virgo logs: C:\ProgramData\VMWare\vCenterServer\logs\vsphere-client\logs

Plugin logs and other files: C:\Users\vspherewebclientsvc\AppData\Roaming\VMware\scaleio

Plugin location C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere-client-serenity

Linux:

Virgo logs: /var/log/vmware/vsphere-client/logs

Plugin logs and other files: /etc/vmware/vsphere-client/vc-packages/scaleio

Plugin location: /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity

yes, i restarted vsphere re-registered plugin relaunched deployment, but it not helped.

Hi,

i'm using vc6u1 on win2012r2 with 2014sql and 4 node esx 6u1 with external apple xraid FC disks directly attached to each node

In plugin logs folder only serverConfig.cfg and certificates folder.

This is indeed the same issue that was fixed for 1.32.5 (some DataStores are returned from the VC without metadata).

This issue will be resolved for 2.0.0.1 (v2.0 Patch1) to be released in ~1.5 month.

Not entirely clear why some DSs are returned without metadata, but a possible workaround might be to select the Datastore in the Deployment wizard step where you configure the SVMs IPs, and not leave it as Automatic.

Perhaps if you create a new local DS for each ESX and select it specfically in the deployment wizard.

Hope that will help.