Operational Defect Database
BugZero updated this defect 37 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 96868
VMware Aria Operations 8.16 Hot Fix 1
Last update date:
4/12/2024
Affected products:
Aria Operations
Affected releases:
8.16
Fixed releases:
No fixed releases provided.
Description:
Details
VMware Aria Operations 8.16 Hot Fix 1 is a public Hot Fix that addresses the following issues: Importing integrations accounts from a single page from Aria Operations SaaS to on-prem setup failsExport / Import SDMP cloud account doesn't workInappropriate message on the Launchpad page after adding VVF/VCF permanent licensed vCenter adapter instancesWhen there are permanent and non-permanent licensed vCenter adapter instances available, the non-permanent license gets displayed on the Licensing page[ST] Aria Operations - License status message needs to be enhanced when inactivePagination of the REST API call doesn't work properly on WLP-History, Custom Datacenters chargeback Notification Rules GET APIs Global Settings: Name and description of several global settings needs to be updatedNotifications: UI: Object Type clear doesn't workNotifications: UI: Object Details doesn't show Custom Properties from templatesAfter the upgrade process, the VVF/VCF-related license info is updated after nearly an hourThe message on the "License Expired" window is updatedvcopsgfsh.py and vcopsgfsh.sh scripts fail to runWebhook Payload Template: Some Parameters contain spaces in their names, and it leads to inability to create Webhook template using that parameters.The "Aria Operations" should be changed to "VMware Aria Operations"Cost: "Total Cost of Ownership" value is negative[vCenter MP] Property Domain Membership Status is not updated[Aria Operations remote client] VC remote plugin registration failed when Aria Operations node does not have FQDN Evaluation and entitlement licenses are displayed in the described casePayload Templates are removing space from string variables The following CVEs have been resolved as of version 8.16 Hot Fix 1: Note: Inclusion of a given CVE in the following table does not imply exploitability of said CVE. Component NameCVEc-aresCVE-2024-25629chromiumCVE-2023-4369CVE-2023-6345CVE-2023-6350CVE-2023-6351CVE-2023-6508CVE-2023-6509CVE-2023-6510CVE-2023-6511CVE-2023-6702CVE-2023-6703CVE-2023-6704CVE-2023-6705CVE-2023-6706CVE-2023-6707CVE-2023-7024CVE-2024-0222CVE-2024-0223CVE-2024-0224CVE-2024-0225CVE-2024-0333CVE-2024-0517CVE-2024-0518CVE-2024-0519CVE-2024-0804CVE-2024-0805CVE-2024-0806CVE-2024-0807CVE-2024-0808CVE-2024-0809CVE-2024-0810CVE-2024-0811CVE-2024-0812CVE-2024-0813CVE-2024-0814CVE-2024-1059CVE-2024-1060CVE-2024-1077CVE-2024-1283CVE-2024-1284CVE-2024-1669CVE-2024-1670CVE-2024-1671CVE-2024-1672CVE-2024-1673CVE-2024-1674CVE-2024-1675CVE-2024-1676CVE-2024-1938CVE-2024-1939CVE-2024-2173CVE-2024-2174CVE-2024-2176cryptographyCVE-2023-49083CVE-2023-50782CVE-2024-26130libuvCVE-2024-24806libvpxCVE-2023-44488CVE-2023-5217CVE-2023-6349linux_kernelCVE-2023-52435CVE-2023-52595CVE-2024-1086CVE-2024-1151CVE-2024-23849CVE-2024-23850CVE-2024-25741CVE-2024-25744CVE-2024-26593CVE-2024-26600CVE-2024-26602CVE-2024-26615CVE-2024-26625vimCVE-2024-22667
Solution
VMware Aria Operations 8.16 Hot Fix 1 can be applied to any 8.16.x environment. Note: Upgrading from older versions directly to this Hot Fix is not supported. You must upgrade to 8.16.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. Download the VMware Aria Operations 8.16 Hot Fix 1 PAK file from the VMware Patch Portal. Note: Select VMware Aria Operations as the Product and select 8.16 as the version and click Search. Select the option below. Release NameRelease DateBuild NumberUI Build NumberFile NameVMware-Aria-Operations-8.16-HF13/26/202423529652 23529657vRealize_Operations_Manager_With_23529652.pak 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.
