Upgrades to version 8.16 or later are not permitted if Remote Collectors or converted Cloud Proxies are in use.
Therefore, it is necessary to replace all Remote Collectors with Cloud Proxies to proceed with the upgrade.
If you try upgrading to 8.16 or later version with Remote Collectors still present, the upgrade will fail and you may receive the error "FailedThe PAK action "new_validate" script "source ./pak_python_wrapper.sh validate.py"
For 8.12 and 8.14 versions if your Remote Collector is no longer collecting data you may also want to consider redeploying as a Cloud Proxy
Environment
VMware Aria Operations 8.12.x and later
Cause
From version 8.16 onwards, Remote Collectors and Lite Cloud Proxies (converted Remote Collectors with restricted features) are no longer supported.
Upgrading to version 8.16 or later requires mandatory redeployment of all Remote Collectors / Lite Cloud Proxies with Cloud Proxy.
Resolution
Document Network Configuration: Record the network settings of the Remote Collector to facilitate the redeployment of the Cloud Proxy.
From Appliance CLI:
# cat /opt/vmware/etc/ovfenv.xml
From 'vApp Options' section in vCenter UI.
Power Off: Shut down the Remote Collector using vCenter UI.
Delete the Remote Collector: From the Aria Operations UI, navigate to Cloud Proxies section and remove the existing Remote Collector.
Note:
- For versions 8.17 or lower, select Data Sources -> Cloud Proxies
- For versions 8.18.X , select Administration -> Cloud Proxies
The 'Download Cloud Proxy OVA' does not redirect to Broadcom Support URL in Aria Operations v8.16 and lower, To download the Cloud Proxy OVA, Click Here and select the current version. Note: For version 8.17 and later Click Add, Click 'Broadcom support portal', log in using your credentials. Select the Aria Operations version and download the cloud proxy OVA file.
Deploy OVA: Use the following document to deploy the OVA from vCenter: Deployment Guide
Verify Deployment: Once the deployment is complete, check the Cloud Proxies section to confirm the successful deployment of the new Cloud Proxy.
Additional Information
Make sure to change the data collection from the Cloud Proxy to the default collector until the Cloud Proxy is redeployed. If you do not switch to the default collector, data collection will cease from the moment we shut down the Remote Collector until a new Cloud Proxy is deployed.
If you are using a collector group, you must add new Cloud Proxies and remove the Remote Collectors from the collector group.
It is recommended that if you are not already using a collector group, create a new collector group and add newly deployed Cloud Proxies into it. Reassign all adapter instances that were previously associated with Remote Collectors to the newly created collector group.