This is a known issue impacting VMware NSX.
Workaround:
Use the following steps to clean up the Data Collection group so that it contains the valid policy path, this will disable NSX intelligence data collection for the cluster, thus removing the system group used and then recreate the data collection and a new system group containing all the hosts again.
1. Fetch the NSX Application Platform (NAPP) registration results using the following API request.
GET /policy/api/v1/infra/sites/napp/registration
2. Set the the NSX Intelligence enablement to false using the following API request and the cluster_id info from the registration API request results (step 1). Make sure to have "is_intelligence_enabled": false" in the PATCH API request payload.
PATCH /policy/api/v1/infra/sites/napp/registration/<cluster_id> { "cluster_id" : "<cluster_id>", "is_intelligence_enabled" : false }
3. Set the NSX Intelligence enablement back to true using the same API. Make sure to have "is_intelligence_enabled": true" in the PATCH API request payload.
PATCH /policy/api/v1/infra/sites/napp/registration/<cluster_id> { "cluster_id" : "<cluster_id>", "is_intelligence_enabled" : true }