This issue is resolved in VMware Aria Automation 8.16.0. See the Workaround section below for additional details.
Workaround:
Prerequisites
- You have SSH access to the appliances running in the cluster.
- You have root username and password to login to the appliances.
Procedure
- Acquire the associated vSphere account id:
- For vCF: take the last segment from the url in customProperty "vsphere"
- For VMC: take the last path segment from the "cloud-account" property of "_links" property in "enabledRegions" list.
- Using curl run a GET against /iaas/api/cloud-accounts/account-id
curl --location --request GET 'https://AriaAutoFQDN/iaas/api/cloud-accounts/account-id' \ --header 'Authorization: Bearer cloud_admin_token'
Note: Update account-id with your correct cloud account ID.
Note: Update cloud-admin-token with the correct bearer token.
Note: Update AriaAutoFQDN with your correct FQDN.
- PATCH in new properties to reset the enumeration state using /provisioning/uerp/resources/endpoints/last-segment-uuid
curl --location --request PATCH 'https://AriaAutoFQDN/provisioning/uerp/resources/endpoints/last-segment-uuid' \
--header 'Authorization: Bearer cloud-admin-token' \
--header 'Content-Type: application/json' \
--data-raw '{
"entriesToAdd": {
"customProperties": {
"endpointHealthCheckState": "AVAILABLE",
"consecutiveFailuresCount": "0",
"lastFailureTimestampMillis": "0"
}
},
"kind":"com:vmware:xenon:common:ServiceStateMapUpdateRequest"
}'
Note: Update AriaAutoFQDN, last-segment-uuid, and cloud-admin-token with the correct information.