Just got the issue fixed by support. EDIT:: This is a "good" fix.  Issue has never come back.  The instructions pertains to VCSA (Not windows server.)

As folks have noted, it is a known issue in vCenter 6 Update 1 (VCSA,) but I recall having the issue some when I was running vCenter 6.  The fix appears to legitimately take care of the problem, not just turn off stateless alarms in whole.  I mentioned to my support rep that a bunch of folks would appreciate a KB article on this, but until one comes out, here are the steps.  Sorry they are a bit generic, but hoping you can follow.

1) Log into vCenter. Go to Alarm Settings --> Health status changed alarm --> Edit Settings -->

2) Under Triggers --> Change Status from Unset to Warning.  In advanced options on the same page --> Add argument data center name --> Operator as equal to --> Value is Data Center name.

3) Restart the vCenter Server Services by logging in via Putty, running "service-control --stop vmware-vpxd" then "service-control --start vmware-vpxd"

Hope this helps some folks!