You can try following workarounds
Workaround: You can use one of the following options to resolve this issue:
- Restart the VMware vSphere Profile-Driven Storage Service.
- Move the host outside the cluster and add it back.
- If none of the storage providers are listed, when you navigate to the Storage Providers drop-down menu, move all the hosts to a new Virtual SAN enabled cluster.
This seems to be known issue in esx 5.5 u1
vCenter Server 5.5 Update 1 Release Notes
Let me know if this works for you
Thanks
Arvind