VMware Aria Operations 8.12 Hot Fix 6

Products

• VMware Aria Suite

Issue/Introduction

VMware Aria Operations 8.12 Hot Fix 6 is a public Hot Fix that addresses the following issues:

• Handle NULL values in VM's "CloudAutomation|CustomProperties" for the CloudZone ID.
• Service Credential Token is not serializable, which breaks adding new nodes to existing instances.
• vcloud adapter doesn't collect data, the UI: shows " Failed to Login : begin 0, end -1, length 0".
• SDDC MP is not installed on all nodes.
• KPI latency metrics for vSAN clusters in vCenter reporting 0.

Environment

VMware Aria Operations 8.12.x

Resolution

vRealize Operations 8.12 Hot Fix 6 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 6 PAK file from the Broadcom Support Portal.

Note: You will need to login to the portal first then click the link above in order to allow download of the file.

Release Name	Release Date	Build Number	UI Build Number	File Name
VMware-Aria-Operations-8.12-HF6	12/22/2023	22976212	22976215	vRealize_Operations_Manager_With_CP-8.x-to-8.12.1.22976212.pak

2. Log in to the primary node VMware Aria 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 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.