VMware Aria Operations 8.16.1
Article ID: 324330
Updated On:
Products
VMware Aria Suite
Issue/Introduction
This article covers the fixes made in VMware Aria Operations 8.16.1 from previous versions.
The following issues have been resolved as of Aria Operations 8.16.1:
The following issues have been resolved as of Aria Operations 8.16.1:
- Workload Threshold setting, set in the Policy for the Datastore, is not taken properly by the WLP
- tcpdump installation failed
- Add instructions in CASA API Guide to upload a custom cert with password
- [vROps remote plugin] Dashboards of AriaOps remote plugin fail to show in vCenter UI with 401 Unauthorized Error message
- "Go to Original Resource" link for the aggregated objects in the objects details page navigate to the undefined page
- The "Alert List" widget is not updated after editing the output filter
- Download percent of Cloud Proxy is not displayed during the upgrade process
- Super Metric value is being calculated wrong when using the isFresh() function on multi-node setups
- vROPS adding support of vCLS 2.0 VMs
- [CP] - getting the "Invalid Date" value under the "Date & Time Created" column of Support Bundle page
- Negated symptoms create a NPE when sending Alert Notification
- Webhook Payload Template: "Webhook Plugin Throws Null Pointer Exception When Using "CPU|CPU limit (MHz)" Property in Payload Template
- Dashboard UI loading in redirection loop for user with limited role
The following CVEs have been resolved as of vRealize Operations 8.16.1:
| Component | CVE |
| bind | CVE-2023-4408 |
| CVE-2023-50387 | |
| CVE-2023-50868 | |
| CVE-2023-5517 | |
| CVE-2023-5679 | |
| CVE-2023-6516 | |
| giflib | CVE-2023-39742 |
| CVE-2023-48161 | |
| glibc | CVE-2023-0687 |
| CVE-2023-4813 | |
| jdk-liberica | CVE-2024-20918 |
| CVE-2024-20926 | |
| CVE-2024-20952 | |
| jvm-hotspot-openjdk | CVE-2024-20918 |
| CVE-2024-20919 | |
| CVE-2024-20921 | |
| CVE-2024-20926 | |
| CVE-2024-20945 | |
| CVE-2024-20952 | |
| libpng | CVE-2022-3857 |
| linux-pam | CVE-2024-22365 |
| linux_kernel | CVE-2023-50431 |
| CVE-2023-52436 | |
| CVE-2023-52438 | |
| CVE-2023-52439 | |
| CVE-2023-6040 | |
| CVE-2024-0340 | |
| CVE-2024-0565 | |
| CVE-2024-0607 | |
| CVE-2024-0646 | |
| CVE-2024-1312 | |
| nss | CVE-2023-0767 |
| openssl | CVE-2017-3735 |
| CVE-2017-3736 | |
| CVE-2017-3737 | |
| CVE-2017-3738 | |
| CVE-2018-0732 | |
| CVE-2018-0734 | |
| CVE-2018-0737 | |
| CVE-2018-0739 | |
| CVE-2018-5407 | |
| CVE-2019-1547 | |
| CVE-2019-1551 | |
| CVE-2019-1552 | |
| CVE-2019-1559 | |
| CVE-2019-1563 | |
| CVE-2020-1968 | |
| CVE-2020-1971 | |
| CVE-2021-23840 | |
| CVE-2021-23841 | |
| CVE-2021-3712 | |
| CVE-2021-4160 | |
| CVE-2022-0778 | |
| CVE-2022-1292 | |
| CVE-2022-2068 | |
| procps | CVE-2023-4016 |
| runc | CVE-2023-25809 |
| CVE-2023-27561 | |
| CVE-2023-28642 | |
| shim | CVE-2022-28737 |
| CVE-2023-40546 | |
| CVE-2023-40547 | |
| CVE-2023-40548 | |
| CVE-2023-40549 | |
| CVE-2023-40550 | |
| CVE-2023-40551 |
Resolution
VMware Aria Operations 8.16.1 can be applied to any 8.10.x - 8.14.x, 8.16 environment.
It is recommended to take snapshots following How to take a Snapshot of VMware Aria Operations before upgrading.
- Download the VMware Aria Operations 8.16.1 upgrade PAK file from 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
