VMware Aria Operations 8.12 Hot Fix 3
search cancel

VMware Aria Operations 8.12 Hot Fix 3

book

Article ID: 336697

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

VMware Aria Operations 8.12 Hot Fix 3 is a public Hot Fix that addresses the following issues:
  • Handle Multiple PSC Hosts in APPOSAdapter configuration.
  • [Dashboards] Some issues in UI when Log Analysis widget is added.
  • Wrong metrics result when selecting a VDC Organization object type in Policies page.
  • View is excluding content based on instance break down column.
  • [Collector Group] Adding Remote Collector to a new or existing App-Monitoring HA disabled collector group fails.
  • [Collector Group] Warning message for adding RC to a new or existing App-Monitoring HA enabled collector group is not proper.
  • [Collector Group] Collector group column value should show proper information to which group belongs CPs and detached RCs.
  • [App Monitoring] The remote collector is allowed to select from the "Installing Telegraf Agent" wizard.
  • [VCF] The VCF datacenters are not listed in the cost drivers page.
  • [Reports] The background color of some views remains dark regardless of the color scheme.
  • [VCF] api.connection.timeout property in config.properties is not honoured in VCF adapter.
  • Cloud proxy update failed due to premature update of server.root.ca.pem.
  • Power consumption widget in the sustainability page of Aria Ops is not displaying data.
The following CVEs have been resolved as of version 8.12 Hot Fix 3:
ComponentCVE
bindCVE-2023-2828
CVE-2023-2829
CVE-2023-2911
consulCVE-2021-41803
CVE-2022-40716
CVE-2023-2816
containerdCVE-2022-31030
etcdCVE-2021-28235
CVE-2023-0296
CVE-2023-32082
golang-runtimeCVE-2022-41722
CVE-2022-41724
CVE-2022-41725
CVE-2023-24532
CVE-2023-24534
CVE-2023-24536
CVE-2023-24537
CVE-2023-24538
CVE-2023-24539
CVE-2023-24540
CVE-2023-29400
CVE-2023-29402
CVE-2023-29403
CVE-2023-29404
CVE-2023-29405
libuvCVE-2020-8252
linux_kernelCVE-2023-3006
CVE-2023-3090
CVE-2023-3111
CVE-2023-32247
CVE-2023-32248
CVE-2023-32249
CVE-2023-32250
CVE-2023-32251
CVE-2023-32252
CVE-2023-32253
CVE-2023-32254
CVE-2023-32255
CVE-2023-32256
CVE-2023-32257
net-snmpCVE-2022-24805
CVE-2022-24806
CVE-2022-24807
CVE-2022-24808
CVE-2022-24809
CVE-2022-24810
ntpCVE-2023-26551
CVE-2023-26552
CVE-2023-26553
CVE-2023-26554
CVE-2023-26555
spring-security-coreCVE-2023-34034
CVE-2023-34034
prometheusCVE-2019-3826
shadowCVE-2023-29383
sqlite3CVE-2022-35737
sysstatCVE-2023-33204
vimCVE-2023-2609
webkitCVE-2023-32445
CVE-2023-38133
CVE-2023-38572
CVE-2023-38592
CVE-2023-38594
CVE-2023-38595
CVE-2023-38597
CVE-2023-38599
CVE-2023-38600
CVE-2023-38611


Environment

VMware Aria Operations 8.12.x

Resolution

vRealize Operations 8.12 Hot Fix 3 includes all the fixes delivered in Patch Releases/Hot Fixes released prior and can be applied to any 8.12.x environment.
Note: Upgrading from older versions directly to this Hot Fix is not supported.  You must upgrade to 8.12.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. Download the VMware Aria Operations 8.12 Hot Fix 3 PAK file from the VMware Patch Portal.
Note: Select VMware Aria Operations as the Product and select 8.12 as the version and click Search.
Select the option below.
Release NameRelease DateBuild NumberUI Build NumberFile Name
VMware-Aria-Operations-8.12-HF38/10/20232223626722235728vRealize_Operations_Manager_With_CP-8.x-to-8.12.1.22236267.pak
  1. Log in to the primary node VMware Aria Operations Administrator interface of your cluster at https://master-node-FQDN-or-IP-address/admin.
  2. Click Software Update in the left panel.
  3. Click Install a Software Update in the main panel.
  4. Follow the steps in the wizard to locate and install your PAK file.
  5. Install the product update PAK file.
    Wait for the software update to complete. When it does, the Administrator interface logs you out.
  6. 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.
  7. 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.
     
  8. 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.
Powered by Wolken Software