I know there are storage policies. And all VSAN storage provider are online and synced
Any idea? We are running 6.2. vsphere build 6765062.
Check if you can create a Storage Policy using the button to better scope what is working or not.
What version of vCenter is in use?
Any changes in the environment since SPs were last visible? (e.g. firewalls, certs, updates).
Have you tried a different browser?
Have you tried restarting the Web Client services on the vCenter?
Check spbm functionality/health/compliance via RVC (e.g. spbm.check_compliance <pathToVM>).
I tried to restart vmware-sps services on vCenter appliance and vsanvpd on hosts
We are running 184.108.40.206200 build 5326079
VCSA was restarted as well
All VMs are compliant with our policy and I can check compliance via gui.
I can create a test policy but as soon as I create it it is missing from the window - it is there but showing in GUI.
Seems it is likely either a Browser or Web-Client issue so.
Have you tried other browsers and/or from another computer/source?
What changes in the environment have occurred since this last functioned normally?
Have a look in the virgo logs of the Web-Client to perhaps get more information as to what is being pulled/processed when you access the Storage Policy page.
it looks like it is permission issue - very interesting
my account belongs to two different groups - one with admin access, one with read-only access. It looks like the real-only access overwrites the admin access! If I remove myself from read-only group, then I will be able to see all storage policy
This is must be a bug - this permission behavior happens on some of the operations (like this one, "seeing storage policy") but not others
Anyone can reproduce the problem?
Fairly certain that is expected behaviour:
"If you are logged in as a user that is member of the administrators group you have full access to the vCenter Server at every object level by default. If you are member of another group that was granted read only or restrictive rights to a particular object, the most restrictive permission applies on that object, overriding the administrator permission that may have been propagated from a higher level."
The reason why you are seeing it for some things and not others depends on the privileges of the Read-only role (e.g. Profile-driven Storage View is unticked for this role)