VMware Aria Operations 8.17.2
Article ID: 368977
Updated On:
Products
VMware Aria Suite
Issue/Introduction
This article covers the fixes made in VMware Aria Operations 8.17.2 from previous versions.
The following issues have been resolved as of Aria Operations 8.17.2:
- Snapshot age reporting incorrectly
- [App Monitoring] Product managed telegraf agent installation via script fails due to wget.exe URL is not reachable from Windows machine to CP
- Reclamation page show >0 days old snapshots with 0 GB reclaimable space
- Update Messaging in Manage Agents page
- Uninstalling ARC agent status for windows-endpoint keeps on loading state when uninstall gets triggered through api.
- Activated plugins is not shown post Agent is tried to uninstall with failed attempts
- [APP Monitoring] : vROPS Large Environment - Bootstrap operation takes 11 mins to complete for 1 VM
- Agent Installation on Windows VM taking more than 5mins
- "Manage Telegraf Agents" page takes 30 sec to load
- [APP Monitoring] : ARC services are operational on the endpoint VM; however, the agent status is currently indicated as unhealthy in vROPS UI
- NPE when sending Alert Notification
- [WLP] [vSAN] During the Workload Optimization, the VM vSAN compatibility check calls are failing, when the endpoint vCenter version is 8.0 U2 and higher
- Cost Calculation failed on one DC.
- [AWLP] [Backend] vRA calls, to get the advanced workload placement plan from vROps, fail on vROps side
- Custom property: Internal server Error is thrown on alerts timeline
- Having "\" and other JSON special characters in notification template leads to invalid JSON payload.
- [Resources API Call] All resources in api response have resourceHealth and Value are GREY and -1 respectively on 8.17.x vROPs
The following CVEs have been resolved as of VMware Aria Operations 8.17.2:
| Component Name | CVE |
| kerberos | CVE-2018-5729 |
| CVE-2018-5730 | |
| less | CVE-2022-48624 |
| CVE-2024-32487 | |
| libyaml | CVE-2024-3205 |
| linux_kernel | CVE-2022-48674 |
| CVE-2023-28746 | |
| CVE-2024-26817 | |
| CVE-2024-26904 | |
| CVE-2024-26924 | |
| CVE-2024-26925 | |
| CVE-2024-26926 | |
| CVE-2024-26928 | |
| CVE-2024-26931 | |
| CVE-2024-26934 | |
| CVE-2024-26935 | |
| CVE-2024-26937 | |
| CVE-2024-26947 | |
| CVE-2024-26950 | |
| CVE-2024-26951 | |
| CVE-2024-26955 | |
| CVE-2024-26956 | |
| CVE-2024-26957 | |
| CVE-2024-26960 | |
| CVE-2024-26961 | |
| CVE-2024-26965 | |
| CVE-2024-26966 | |
| CVE-2024-26969 | |
| CVE-2024-26970 | |
| CVE-2024-26973 | |
| CVE-2024-26974 | |
| CVE-2024-26976 | |
| CVE-2024-26978 | |
| CVE-2024-26979 | |
| CVE-2024-27013 | |
| CVE-2024-27020 | |
| CVE-2024-27032 | |
| CVE-2024-27059 | |
| CVE-2024-27395 | |
| CVE-2024-27396 | |
| CVE-2024-35972 | |
| CVE-2024-35978 | |
| CVE-2024-35982 | |
| CVE-2024-35984 | |
| CVE-2024-35990 | |
| CVE-2024-35997 | |
| CVE-2024-36008 |
Environment
VMware Aria Operations 8.x
Resolution
VMware Aria Operations 8.17.2 can be applied to any 8.10.x - 8.17.x environment.
It is recommended to take snapshots following How to take a Snapshot of VMware Aria Operations before upgrading.
- Download the VMware Aria Operations -Virtual Appliance upgrade pak file from the Broadcom Support Portal.
- Log in to the primary node Aria Operations Administrator interface of your cluster at https://primary-node-FQDN-or-IP-address/admin.
- Click Software Update in the left panel.
- Click Install a Software Update in the main panel.
- Follow the steps in the wizard to locate and install your PAK file.
- Install the product update PAK file.
Wait for the software update to complete. When it does, the Administrator interface logs you out. - Log back into the master node Administrator interface.
The main Cluster Status page appears and cluster goes online automatically. The status page also displays the Bring Online button, but do not click it.
- Clear the browser caches and if the browser page does not refresh automatically, refresh the page.
The cluster status changes to Going Online. When the cluster status changes to Online, the upgrade is complete.
Note: If a cluster fails and the status changes to offline during the installation process of a PAK file update then some nodes become unavailable. To fix this, you can access the Administrator interface and manually take the cluster offline and click Finish Installation to continue the installation process.
- Click Software Update to check that the update is done.
A message indicating that the update completed successfully appears in the main pane.
Feedback
Yes
No
Powered by
