VASA Storage providers missing in VCSA 8.0
search cancel

VASA Storage providers missing in VCSA 8.0

book

Article ID: 314001

calendar_today

Updated On:

Products

VMware vCenter Server 8.0

Issue/Introduction

VASA Storage providers are missing.

Unable to create a new VM, and vCLS VMs are not getting created

 

Cause

SPS solution user is not a member of the administrators group of the SSO domain (vsphere.local)

 

On sps.log, found:

YYYY-MM-DD HH:MM:SS [main] INFO opId=sps-Main-394888-997 com.vmware.vim.storage.common.task.CustomThreadPoolExecutor - [VLSI-client] Active thread count is: 20, queue size: 96
YYYY-MM-DD HH:MM:SS [main] DEBUG opId=sps-Main-394888-997 com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientImpl - Login request made for VPXD client.
YYYY-MM-DD HH:MM:SS [main] DEBUG opId=sps-Main-394888-997 com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientImpl - Wait duration for timeout to vpxd client is 1800
YYYY-MM-DD HH:MM:SS [main] WARN opId=sps-Main-394888-997 com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientImpl - loginByToken request timedout, cancelling the task scheduled
YYYY-MM-DD HH:MM:SS [main] ERROR opId=sps-Main-394888-997 com.vmware.vim.storage.common.task.retry.CallableRetryDecorator - Caught exception -
com.vmware.vim.storage.common.serviceclient.vpxd.VpxdException: Error while doing login to VPXD service
at com.vmware.vim.storage.common.serviceclient.vpxd.VpxdException.fromEx(VpxdException.java:53) ~[storage-commons-1.0.jar:?]
at com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientImpl.loginByToken(VpxdClientImpl.java:175) ~[storage-commons-1.0.jar:?]
at com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientLifeCycle.login(VpxdClientLifeCycle.java:82) ~[storage-commons-1.0.jar:?]
at com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientLifeCycle.login(VpxdClientLifeCycle.java:23) ~[storage-commons-1.0.jar:?]
at com.vmware.vim.storage.common.serviceclient.ConnectionInitializationTask$CallableTemplate.call(ConnectionInitializationTask.java:118) ~[storage-commons-1.0.jar:?]
at com.vmware.vim.storage.common.task.retry.CallableRetryDecorator.call(CallableRetryDecorator.java:64) ~[storage-commons-1.0.jar:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_362]

Resolution

Use an LDAP browser (ex: jxplorer) and connect to the vCenter LDAP database.

 

Using jxplorer: Using JXplorer to connect to the vSphere Single Sign-on

  1. On the right pane, expand in Table Editor
  2. Navigate to local>vsphere>builtin>administrators

 

SSH to the affected vCenter and follow the steps:

 

1. Get the machine ID from the affected VC:

/usr/lib/vmware-vmafd/bin/vmafd-cli get-machine-id --server-name localhost

3d2aab75-9f79-4c38-91e2-6cefc6727ba8  <<< Sample output

2. Check the administrators group for a missing entry, e.g:

CN=sps-3d2aab75-9f79-4c38-91e2-6cefc6727ba8,CN=ServicePrincipals,DC=vsphere,dc=local3.

If the entry is missing, recreate it.

NOTE: In this example SSO domain name is the default "vsphere.local" and this should be reflected in the missing entry you create:CN=sps-3d2aab75-9f79-4c38-91e2-6cefc6727ba8,CN=ServicePrincipals,DC=sso,DC=domain

3. Add the missing entry using jxplorer to the administrators group

4. Restart sps using the command: service-control --restart vmware-sps