VM Storage Policy Compliance Out of Date

[ntcharhan]

Hi all!

A lot of my VMs have the VM Storage Policy Compliance Out of Date.

When running a manual check on the policy I get this error message:

The "Check VM Storage Policy Compliance" operation failed for the entity with the following error message.

com.vmware.vim.binding.vmodl.fault.SystemError:

reason = Invalid fault

inherited from com.vmware.vim.binding.vmodl.fault.SystemError: java.util.concurrent.ExecutionException

Anyone know why this is happening?

Best regards,

Harald Hansen

NTC Services AS

[zdickinson]

I am wondering if this is an underlying vCenter Server issue.  Have you recently upgraded vCenter or replaced certificates or had a certificate expire?  Thank you, Zach.

[ntcharhan]

I've wondered about the same, as I've seen some similar error messages in cases related to VMware, but not VSAN.

The vCenter install is fresh, about a month old, on the latest version (5.5.0 Build 2414847), running on vCenter Appliance version 5.5.0.20400 Build 2442330. I've planned to replace the certs with valid ones from my CA, but haven't gotten to it.

The default certs are valid until 2025.

[zdickinson]

Doesn't sound like a vCenter issue then.  The solution sounds out of my league and would be a support call.

On a side note, I'm getting conflicting information on the vCenter Appliance.  It seems like the direction VMware would like you to go.  I tried it with my new vSAN, and it was a train wreck.  Services would stop, it would crash, errors in the VIC, errors in the Web Client, etc...  Every time I called up support they would help, of course, but each tech said they hated working on it and would like to see the Windows version.  Then I read Mr. Lam (virtuallyGhetto), and he loves it.

I ended up replacing the appliance with the Windows version and have had no issues since.  Thank you, Zach.

[ntcharhan]

I talked with support and after a couple messages we decided to reboot all hosts.

The problem was solved after the master node was rebooted; you'll find which by logging in to each node and issuing the esxcli vsan cluster get command.

Now I've have to reapply all policies to my VMs, which is a bit of a hazzle.