You'll want to check storage provider status on your VSAN cluster, if something is wrong with the storage provider/SMS layer, you'll have problems with any of storage policy functionality such as editing or creating new storage policies.
Check page 10-11 under Verify the Storage Provider status in the POC: https://www.vmware.com/files/pdf/products/vsan/VMware_Virtual_SAN_POC_Guide.pdf
I don't see any problem in storage provider status. there isn't any error with vSAN except java.lang error when I want to edit a policy.
are u tried below steps ??
During creation of new policy I also see this error
I have the same issue. Was then any resolution?
thanks
Hey, Any solution?
I know that I`ll sound like KO here, and I`ll be just another one who said this, but WebClient was a big mistake:/
Anyway, looks like guys here had similar issues:
https://communities.vmware.com/message/2478071
Hope that going to help
Good morning, don't know if this will help; adding the port 9443 has fixed several issues we have had. https://vcenter:9443/vsphere-client
I agree with the Web Client, I only go there if I have to. Thank you, Zach.
Hi,
I am running an Hybrid vSAN and have the similar issue.
Do we have a solution for this?
Thanks.
--Ramesh
Hello,
I have the same issue only when I try to manage a Policy VSAN. This error didn't exist in the past.
Does anyone get a KB to resolve this issue?
Thank you
Hello NTAV,
Welcome to Communities.
Can you please provide more information:
- What build (Not version, build number e.g. 14320388) do ESXi and vCenter have installed?
- Which Client are you using?
- Are there other issues in the cluster like applying/changing Storage Policies in use by VMs?
- Are all the VASA providers online and at least one showing as active?
- All checks in vSAN Health are Green?
I would advise (if possible) you open a Support Request with GSS to look at this as there can potentially be abroad range of causes, some related to vSAN and others not (e.g. works in Firefox but not in Chrome).
Bob
Hello,
After the reboot of one host VSAN this morning the issue has disappeared. Now it’s possible to check or modify storage policy of all VM.