This was indeed an issue that has been fixed in vSphere 6.5 U2, and 6.7 U1 (see VMware vCenter Server 6.7 Update 1 Release Notes )
