VMware Aria Operations 8.17.1

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

This article covers the fixes made in VMware Aria Operations 8.17.1 from previous versions.

The following issues have been resolved as of Aria Operations 8.17.1:

• [Policy] It would be better to change the info message for the reorder Policies
• Payload Template: No Error Message for Duplicate Metric Addition in Payload Template
• Newly created resources are loaded using old Policy content
• Payload Template: NullPointerException when Changing Outbound Method of In-Use Payload Template
• Payload Template: Unclear Metric Limitation
• Capacity metrics are populated with zero on data collection issues
• "Edit Alerts" and "Edit Symptoms" under Policy menu are not visible in Object Browser
• The alert regarding the license usage should not be triggered for the subscription-based license keys
• [Dashboards: Alert List] Dashboard created with the "Alert List" widget is not refreshed automatically for "Group by: None"
• [Reports]The generated report renders empty for some resource types
• Operations upgrade to 8.14 fails when 'SSLFIPS on' is added to httpd.conf
• [vROps remote plugin] AriaOps initial configuration wizard is not rendered properly in the "VMware Aria Operations" page of VC
• Capacity metrics are populated with zero on data collection issues
• [vRops remote client] The text and input fields on all pages of the AriaOps initial configuration wizard are not properly shown in the "VMware Aria Operations" page of the vCenter Client with version 8.0.3
• [vROps remote plugin] The AriaOps icon is an old vrops icon in the vCenter client
• [vRops remote plugin] The AriaOps plugin version is hardcoded and the value is 8.11.2 in case of AriaOps install from VC client
• "Edit Alerts" and "Edit Symptoms" menu items under Policy menu are not visible in the described case
•  Infrastructure Health: "Availability (Ping)" metric value is 0 although the app is available

The following CVEs have been resolved as of VMware Aria Operations 8.17.1:
 

Component Name	CVE
org.springframework.security:spring-security-core	CVE-2023-34042
	CVE-2024-22257
org.springframework.security:spring-security-web	CVE-2023-34042
	CVE-2024-22257
postgresql	CVE-2024-0985
	CVE-2024-24213

Resolution

VMware Aria Operations 8.17.1 can be applied to any 8.10.x - 8.16.x environment.

It is recommended to take snapshots following Snapshot Creation in VMware Aria Operations before upgrading.

1. Download the VMware Aria Operations 8.17.1 upgrade PAK file from Broadcom 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 pane.