The error shows that
'This cluster ownership is owned by another instance of NSX and can be viewed in read-only mode.
Configuration data that is inaccessible and cannot be retrieved is marked as Unknown.'
This happens when trying to activate NSX Intelligence within NAPP deployment, and when trying to modify NSX Intelligence Settings on the clusters, there is a lock by the Cluster name and the Collection Status is 'Unknown'
Follow workaround
Workaround:
Run the following API command against the VIP of the NSX Manager
GET https://localhost/napp/api/v1/intelligence/data-collection/clusters?cluster_type=HOST_CLUSTER
you will receive something similar to
{
“cluster_id”: “########-####-####-####-########b872:domain-c37",
“cluster_type”: “HOST_CLUSTER”,
“display_name”: “display-name”,
“id”: “########-####-####-####-########b872:domain-c37",
“enabled”: true,
“member_list”: [
“########-####-####-####-########e18c”,
“########-####-####-####-########1dd1"
],
“owner_nsx”: “NONE”,
“resource_type”: “IntelligenceClusterConfig”,
“unique_id”: “########-####-####-####-########3761",
“realization_id”: “########-####-####-####-########3761",
“path”: “/infra/sites/default/intelligence/cluster-configs/########-####-####-####-########b872:domain-c37",
“relative_path”: “########-####-####-####-########b872:domain-c37",
“parent_path”: “/infra/sites/default”,
“compute_manager”: {
“id”: “########-####-####-####-########b872”,
“display_name”: “displayname”,
“server”: “esxi-name”
}
}
replace the parameter in “owner_nsx”: which is “NONE”, to “owner_nsx”: “SELF”, in the body and insert the text back into the JSON body to patch the parameter back into the NSX Manager
{
“cluster_id”: “########-####-####-####-########b872:domain-c37",
“cluster_type”: “HOST_CLUSTER”,
“display_name”: “display-name”,
“id”: “########-####-####-####-########b872:domain-c37",
“enabled”: true,
“member_list”: [
“########-####-####-####-########e18c”,
“########-####-####-####-########1dd1"
],
“owner_nsx”: "SELF”,
“resource_type”: “IntelligenceClusterConfig”,
“unique_id”: “########-####-####-####-########3761",
“realization_id”: “########-####-####-####-########3761",
“path”: “/infra/sites/default/intelligence/cluster-configs/########-####-####-####-########b872:domain-c37",
“relative_path”: “########-####-####-####-########b872:domain-c37",
“parent_path”: “/infra/sites/default”,
“compute_manager”: {
“id”: “########-####-####-####-########b872”,
“display_name”: “displayname”,
“server”: “esxi-name”
}
}
run the following with the updated owner_nsx parameter within the JSON body which is provided above to change ownership of the cluster so it can be accessed
PATCH https://localhost/napp/api/v1/intelligence/data-collection/clusters?cluster_type=HOST_CLUSTER
You will now be able to work with NSX Intelligence on the clusters which you patched with read-write permissions