7.3

If the Test Connection action is successful but some data collection or provisioning operations fail,
you can install the same certificate on all the agent machines that serve the endpoint and on all DEM
machines. Alternatively, you can uninstall the certificate from existing machines and repeat the
preceding procedure for the failing endpoint.
n
The vRealize Automation REST APIs that were used to programmatically create, edit, and delete
endpoints in vRealize Automation 7.2 and earlier are no longer supported in vRealize Automation 7.3
and later. To programmatically create, edit, and delete endpoints in vRealize Automation 7.3 or later
you must use either new vRealize Automation endpoint-configuration-service REST APIs or use
vRealize CloudClient.
n
After you upgrade or migrate from an earlier vRealize Automation installation, if data collection fails
for OpenStack endpoints you can add the
VMware.Endpoint.Openstack.IdentityProvider.Domain.Name custom property to each
Keystone V3 OpenStack endpoint to specify a valid domain name and enable data collection.
n
When you upgrade a third-party IPAM endpoint, such as Infoblox IPAM, the vRealize Orchestrator
package that contains the RegisterIPAMEndpoint workflow is upgraded. You might need to rerun
the workflow in vRealize Orchestrator when the vRealize Automation upgrade is finished.
n
To make a credentials change to multiple endpoints, you can either edit the endpoints individually or
use vRealize CloudClient to perform a bulk update.
n
Some endpoint types, such as vCloud Air and vCloud Director, cannot be upgraded or migrated
directly from vRealize Automation 6.2.x to vRealize Automation 7.3 or greater.
n
After a successful upgrade or migration to vRealize Automation 7.3, if the Infrastructure >
Endpoints page does not show any endpoints or only shows some endpoint types and endpoints,
see Knowledge Base Article 2150252 for a suggested workaround.
Considerations When Deleting Endpoints
You can delete certain endpoint types under certain conditions.
n
You can delete endpoints that have not been data-collected.
n
You can delete an OpenStack, Amazon and VRO endpoint if it has been data collected, but has no
reservations. Other endpoint types cannot be deleted if they have been data collected.
n
You can delete a third-party IPAM endpoint if it has no association to a network profile.
n
When deleting a vSphere endpoint, the confirmation prompt lists the following dependencies:
n
The endpoint has been data-collected.
n
The endpoint is referenced in a reservation that maps to a compute resource. You cannot delete
an endpoint is referenced in a reservation. Reservations require a compute resource.
n
The endpoint contains a template that is referenced in an existing blueprint.
The blueprint is not deleted when you delete the endpoint.
n
The endpoint is used by virtual machines that are in use.
Configuring vRealize Automation
VMware, Inc. 219