vRealize Operations 8.6.2
search cancel

vRealize Operations 8.6.2

book

Article ID: 337330

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

vRealize Operations 8.6.2 is a public maintenance release of vRealize Operations in which issues related to performance and stability have been fixed.  In addition, corner case issues that customers might encounter in their environments during upgrade of the product have also been fixed.

The following issues have been resolved as of vRealize Operations 8.6.2:
  • Analytics service of 4 node Medium fails with error "Too many open files".
  • Logging issue during the anlytics startup.
  • NPE thrown in vSAN MP when preferred fault domain name is not set in vSAN API.
  • The cost driver UI does not show total cost and reference cost for labor and license cost driver.
  • Cost calculation is failing with Date Time Parse Exception for VMC datcenter.
  • Information disclosure vulnerability for non logged-in requests
  • [VMC Adapter] Currency property is not plotted in vRealize Operations.
  • [Business Applications] UI crashes on the navigation to any page from the Business Application custom group preview.
  • If agent is installed on a VM using script in previous versions of vRealize Operations, and user tries to install agent again using script with vRealize Operations 8.6, then agent install will fail.
  • The script-based agent installation on Windows VM is failing, if VM has Virtual Adapter (vEthernet) included or excluded by VMTools.
  • The script-based agent installation is failing, if VM has multiple IPs with a single network adapter.
  • Windows Helper script updates Open Source Telegraf configurations as unmanaged for managed VM which "Guest OS IP Address" property and the value of "ipconfig" are different.
  • "CPU Load" and "Disk" metric groups of "Linux OS" objects are not collected in vRealize Operations with Advanced license.
  • When there are no running applications (supported by vRealize Operations), Custom monitoring actions are not available for VM on which telegraf agent is running.
  • Improve messaging for adapter instances of Application Management Pack when vRealize Operations Standard license is applied.
  • Intermittent drop in metrics seen for some VMs as the telegraf buffer gets full.
  • Agent Version number doesn't update post upgrade to 8.6.1

The following CVEs have been resolved as of vRealize Operations 8.6.2:
Component NameCVE
log4jCVE-2021-44228
CVE-2021-45046
golang-runtimeCVE-2021-33195
CVE-2021-33198
CVE-2021-33196
CVE-2021-29923
CVE-2021-38297
CVE-2021-41772
CVE-2021-41771
c-ares CVE-2021-3672


Environment

VMware vRealize Operations 8.6.x

Resolution

Note: Pertaining to CVE-2021-44228 and CVE-2021-45046, the fix contained in vRealize Operations 8.6.2 is not applicable for non-native and Third Party Management Packs.  Non-native and Third Party Management Packs should be upgraded to safe versions.  Failure to do so could leave vRealize Operations vulnerable due to these management packs introducing the security risk.

vRealize Operations 8.6.2 can be applied to any customer's 8.0.x - 8.6 environment.

It is recommended to take snapshots following How to take a Snapshot of vRealize Operations before upgrading.
  1. Download the vRealize Operations 8.6.2 upgrade PAK file from VMware Downloads.
  2. Log in to the master node vRealize Operations Administrator interface of your cluster at https://master-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.
  1. 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.
  1. Click Software Update to check that the update is done.
    A message indicating that the update completed successfully appears in the main pane.

Additional Information

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