VMware Aria Operations 8.18 Hot Fix 2 is a public Hot Fix that addresses the following issues:
The alerts table in the Alerts page no longer retains chosen columns, sorting within the column, and the order of columns.
Kubernetes cost metric not showing - TKGs.
Intermittent UI issues after upgrading to Aria Operations 8.18, including switching to 8.14 UI, black screens, and inconsistent loading.
The link is not working for the "Search Help" button which is placed in the Global Search.
The "Select Object" window does not suggest any metrics/properties after selecting the specific resource while creating a view.
String metric instance name is missing from symptom name in alert details page because of which the symptom was triggered.
In Policy settings, the DT state is deactivated for all attributes, on which there is no defined Symptom Definition.
Double serialization of resource cache in gemfire region.
Property discovery of a testbed with more than 100K objects took 12 hours.
The following CVEs have been resolved as of version 8.18 Hot Fix 2:
Note: Inclusion of a given CVE in the following table does not imply exploitability of said CVE.
Component Name
CVE
apache
CVE-2024-40725
CVE-2024-40898
bind
CVE-2024-1975
CVE-2024-4076
openssl
CVE-2023-0464
CVE-2023-0465
CVE-2023-0466
Environment
VMware Aria Operations 8.18
Resolution
VMware Aria Operations 8.18 Hot Fix 2 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.
* Aria Operations HF2 for version 8.18 to be used in Aria Suite Lifecycle.
Log in to the primary node VMware 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 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.
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.
Once the update is complete delete the snapshots you made before the software update.