Symptom 1:
Failed to create AI resource. Resource with same key already exists
"Symptom 2:
In this case it may be necessary to use the API to delete this old adapter instance to remove from the system completely.
This article provides an example on how to delete an adapter instance from Aria Operations using Swagger API.
Aria Operations 8.x
1. Users are logging in through vCenter SSO credentials, which are exact the same as Active Directory user credentials.
2. This issue may occur after deleting an adapter instance for troubleshooting purposes and then needing to add the adapter back into Aria Operations with the same information.
Solution for Symptom 1:
1. If the adapter instances/integrations are supposed to be there, make sure users are logging in by using the correct SSO or credentials, as vCenter SSO does not have full visibility of the contents.
2. If the above is not the case, below are the steps on deleting an adapter instance from Aria Operations using API:
https://<AriaOpsFQDN>/suite-api/
GET /api/adapters
"{
"adapterInstancesInfoDto" : [ {
"resourceKey" : {
"name" : "VC Adapter",
"adapterKindKey" : "VMWARE",
"resourceKindKey" : "Adapter"
},
"description" : "A vCenter Adapter Instance",
"collectorId" : 1,
"credentialInstanceId" : "UUID",
"id" : "UUID"
} ]
}
: "DELETE /api/adapters/{adapterId}",
replacing adapterId with the ID of the adapter taken from the previous call.
NOTE: We must keep "deleteResources
" option set to false to make sure that existing data for that adapter in not deleted. If set to true, existing data would also be deleted along with the adapter.
Solution for Symptom 2:
https://<AriaOps FQDN>/suite-api
and authorize as admin4. After that, go back to Aria Operations UI and delete that adapter instance.
5. You can re-add the same adapter instance now and it will not give any error.