VMware Aria Operations 8.18.2

Products

• VMware Aria Suite

Issue/Introduction

This article covers the fixes made in VMware Aria Operations 8.18.2 from previous versions:

• Resource Consumption trend view is not displayed for tenant user
• Dashboard created with the "Alert List" widget is not refreshed automatically
• VMSA recommendation link is not found
• Closed alerts incorrectly appear on the App-Level Alerts banner  
• Change the payload single, long string value to type array
• Filter criteria within Views is not returning correct results
• AVS cluster cost is incorrect
• Dynamic property recovery mechanism is not triggered on setups with less than 100k attributes
• Aria Operations views are not working intermittently, so the reports are blank.
• Test Notification fails for multiple resources in descendant case
• Assigned custom property to a specific object will be assigned to all objects incorrectly
• Non-existing VMs deletion time was set to 8.18 upgrade time instead of their real deletion time
• VMC-A NSX-T Adapter throws NPE
• [Platform]: exception from impersonateUser API
• "Open Virtual Machine in vSphere Web client" in Actions menu redirects to incorrect vCenter for some VMs
• Performance issues in AWS MP leading to High Collection Time
• [Product Home Page Dashboards] The dashboard is not added to a product home page in the described case
• Some Rightsizing Metrics Not Being Published
• Telegraf agent installation failures with VCF Ops
• vRO integration with VCF Operations fails with permission errors
• Additional cost driver page does not load properly after the cost calculation when entries related to tag are added
• CA cluster localization is missing in UI message, when trying to replace a node if domains don't have the same state (i.e. ONLINE | OFFLINE).
• Add keep-alive option for chromium in the case when user intensively used reporting
• Aria Operations views are not working intermittently, so the reports are blank.
• Chargeback: Report scheduling mail sender doesn't work
• Enabled policies in alert definition preview window are not updated in the described case
• vSphere Compliance Score cards not visible
• The new snapshot alert is missing
• Fix for using MultiEntityQuery or SingleEntityQuery Map while calling vSAN Perf API's

 

This release resolves CVE-2024-38830, CVE-2024-38831, CVE-2024-38832, CVE-2024-38833, and CVE-2024-38834. For more information on these vulnerabilities and their impact on VMware products, see VMSA-2024-0022. 

Also, the following CVEs have been resolved :

Component Name	CVE
Apache XML Graphics Commons	CVE-2020-11988
google-oauth-java-client	CVE-2020-7692
	CVE-2021-22573
Nimbus-JOSE-JWT	CVE-2023-52428
PostgreSQL Database Server	CVE-2024-7348
Procps	CVE-2023-4016
reactor-netty	CVE-2023-34054
	CVE-2023-34062
sysstat	CVE-2023-33204
Apache Portable Runtime	CVE-2023-49582
linux_kernel	CVE-2022-48872
	CVE-2024-38381
	CVE-2024-38630
	CVE-2024-41096
	CVE-2024-42271
	CVE-2024-42280
	CVE-2024-42284
	CVE-2024-42285
	CVE-2024-42301
	CVE-2024-42302
	CVE-2024-42313
	CVE-2024-42314
	CVE-2024-43858
	CVE-2024-43873
	CVE-2024-43882
	CVE-2024-43900
	CVE-2024-44934
	CVE-2024-44947
	CVE-2024-44974
	CVE-2024-44983
	CVE-2024-44985
	CVE-2024-44986
	CVE-2024-44987
	CVE-2024-44989
	CVE-2024-44998
	CVE-2024-44999
	CVE-2024-45026
	CVE-2024-46673
	CVE-2024-46674
	CVE-2024-46738
	CVE-2024-46743
	CVE-2024-46747
	CVE-2024-46756
	CVE-2024-46757
	CVE-2024-46758
	CVE-2024-46759
	CVE-2024-46782
	CVE-2024-46798
	CVE-2024-46800
	CVE-2024-41071
	CVE-2024-42228
openssl	CVE-2024-5535

Environment

Aria Operations 8.18.2

Resolution

VMware Aria Operations 8.18.2 can be applied to any 8.14.x - 8.18.x environment.

It is recommended to take snapshots following How to take a Snapshot of VMware Aria Operations before upgrading.

1. Download the VMware Aria Operations 8.18.2 upgrade PAK file from the Broadcom Support Portal.
2. Log in to the primary node Aria Operations Administrator interface of your cluster at https://primary-node-FQDN-or-IP-address/admin.
3. Click Software Update in the left panel.
4. Click Install a Software Update in the main panel.
5. Follow the steps in the wizard to locate and install your PAK file.
6. Install the product update PAK file.
   Wait for the software update to complete. When it does, the Administrator interface logs you out.
7. 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.
8. 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.
   
   
9. Click Software Update to check that the update is done.
   A message indicating that the update completed successfully appears in the main panel.