vRealize Operations 8.10 Hot Fix 6

Products

• VMware Aria Suite

Issue/Introduction

vRealize Operations 8.10 Hot Fix 6 is a public Hot Fix that addresses the following issues:

• [SDDC Health] Not existing objects in vRealize Operations 8.6.4 are not automatically removing due to duplicate object.
• Add wal_keep_size setting to vRealize Operations 8.10+ repl db postgresql.conf.
• GCP MP update HTTP request call with Proxy Server details.
• [Analytics] Get an "Internal Server Error" when trying to open Dashboard.
• [NSX-T MP] Duplicate Metric Definition in describe.xml.
• Intermittent ClassLoader related NPE in outbound notification flow.

Environment

VMware vRealize Operations 8.10.x

Resolution

vRealize Operations 8.10 Hot Fix 6 can be applied to any 8.10 environment.
Note: Upgrading from older versions directly to this Hot Fix is not supported.  You must upgrade to 8.10 before applying this Hot Fix.

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

1. Download the vRealize Operations 8.10 Hot Fix 6 PAK file from the Broadcom Support Portal.

Note: Select vRealize Operations Manager as the Product and select 8.10 as the version and click Search.
Select the option below.

Release Name	Release Date	Build Number	UI Build Number	File Name
vROps-8.10-HF6	6/25/2023	21967875	21967879	vRealize_Operations_Manager_With_CP-8.x-to-8.10.2.21967875.pak

2. Log in to the primary node vRealize Operations Manager 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 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 pane.

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