VMware Aria Operations 8.18 Hot Fix 4

Products

• VMware Aria Suite

Issue/Introduction

VMware Aria Operations 8.18 Hot Fix 4 is a public Hot Fix that addresses the following issues:

 

• [VCD MP] Add support to collect non-autocreated vApps
• Slow loading OpenStreetMap resources delay loading on the initial page after login
• VIDM Login flow redirects to the old Aria Ops user interface instead of VCF.
• Create Alert Definition issues
• Response code 500 when trying to create a CIFS plugin instance using the POST /api/alertplugin API call
• Agent is becoming unhealthy intermittently after installing on Windows VM
• Update vcd price policy settings for computeRate/cpuRate
• APUAT: Update links that redirect to the VMware server

The following CVEs have been resolved as of version 8.18 Hot Fix 4:

Component Name	CVE
idna	CVE-2024-3651
DOMPurify	CVE-2024-48910
rsync	CVE-2024-12084
	CVE-2024-12085
	CVE-2024-12086
	CVE-2024-12087
	CVE-2024-12088
	CVE-2024-12747

Environment

VMware Aria Operations 8.18

 

Resolution

VMware Aria Operations 8.18 Hot Fix 4 can be applied to any 8.18.x environment.
Note: Upgrading from older versions directly to this Hot Fix is not supported.  You must upgrade to 8.18.x before applying this Hot Fix.

Important: Take snapshots of each of the VMware Aria Operations nodes before applying the Hot Fix by following How to take a Snapshot of VMware Aria Operations.

1. 1. Download the VMware Aria Operations 8.18 Hot Fix 4 PAK file from the Broadcom Support Portal.

Note: You will need to login to the portal first to allow download of the file using the direct links below.

Release Name	Release Date	Build Number	UI Build Number	File Name
VMware-Aria-Operations-8.18-HF		24575697	24575702	vRealize_Operations_Manager_With_CP-8.14.x-to-8.18.3.24575697.pak  APUAT-for-8.14.x-8.18.3.24576666.pak
vrlcm-vrops-8.18.0-HF4		24575697		vrlcm-vrops-8.18.0-HF4.patch

         * Aria Operations HF4 for version 8.18 to be used in Aria Suite Lifecycle.

             2. Log in to the primary node VMware 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 primary 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.

Once the update is complete delete the snapshots you made before the software update.