"Failed to find the product or its nodes in the provided vCenters. Make sure all the nodes are part of the vCenter's currently provided. If not add missing vCenter's details. Also make sure the credentials for all the provided vCenters are valid. Additionally, verify if the vCenter password saved in locker is consistent with the actual vCenter password. If it is not, update the password in locker and retry.
Failed to find the product in the specified vCenter. vRealize Operations instance with hostname Aria_product_FQDN not found in given vCenter details. Make sure the DNS name field in the vCenter for the node is same as the node hostname and node is powered on in the vCenter Server. Make sure all the nodes are present in the vCenter Servers provided. Else, add the missing vCenter Servers. Ensure the credentials provided for the vCenter Servers are valid or skip the task using the 'Skip vCenter validation' option during retry"
Aria lifecycle manager 8.x
Aria Automation 8.x
Aria Operations 8.x (Including Cloud Proxy)
Aria Operations for logs 8.x
Identity Manager 3.3.x
This can happen if your vCenter validation on Aria Suite Lifecycle fails with an old username/password or username/password has been updated and Aria products still tries to authenticate with an old username/password.
OR
The vCenter managing the Aria product is not added to the Datacenter in Aria suite Lifecycle
Add the vCenter to the Datacenter for Aria Suite Lifecycle, follow the below steps:
Note: Ensure that you have the vCenter fully qualified domain name, user name, and password.
Once the vCenter is added to the Datacenters page, retry the inventory sync and provide with the correct vCenter details:
Workaround for invalid credentials:
NOTE: In the case of a manually added Aria Operations Cloud Proxy, if the Cloud Proxy is added in a separate datacenter, then the data center it has been deployed to needs to be added in Datacenters if it has not been added already.
Once it has been added and validated, the Inventory Sync task may still fail, as Lifecycle does not yet associate that vCenter with the Aria Operations environment. You will need to Retry the task and supply the credentials of the vCenter that the Cloud Proxy was deployed to so that it can be associated to the environment. If multiple proxies have been added, repeat for each hostname or IP that returns the error
Impact/Risks: