Whenever objects are placed with a storage policy of Site disaster tolerance set to either "None - standard cluster" or "None - stretched cluster" this results in locality=None, the components of the same replica can be spread across both the data sites in the cluster.
Then during the subsequent reconfig task, vSAN may decide to reuse the existing components from both sites for 2 different replicas. This causes an issue with the underlying storage layer and the reconfig gets rejected. vSAN may continuously run the same process indefinitely. As end result objects will remain non-compliant forever.