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

• vRealize Operations 8.6.4 Garbled Japanese Characters on vCenter Role Window.
• [VMware Infrastructure Health MP] The deployment and domain objects become Not Existing when the VCF cloud account state is Warning.
• Skipping "/var/log/local6" rotate because parent directory has insecure permissions.
• [Remote Plugin] Deploy 8.0vc, and install vRealize Operations plugin.  Then upgrade vc to 8.0U2, then vRealize Operations does migration, and vRealize Operations page data shows anomalies.
• The vRealize Operation Suite API-CP instance is displayed 2 times in the Product UI.
• [App Monitoring][HA] SAAS Upgrade HA enabled collector group is not getting deactivated.  HA status is shown as Deactivation in progress indefinitely.
• Add appropriate directive to catalina.out rotate configurations to rotate it only if being under admin user and group.
• In config property file of GCVE change URL to production.
• The cost home page does not show AWS, Azure and CP cost from Cloud Health MP.
• [Cloud Providers] Unable to download the cloud providers file.
• Remove validation for gcp service accounts to support same service account for multiple gcp projects.
• Email plugin fails if no credential is selected.
• [Analytics] Get an "Internal Server Error" when trying to open Dashboard.
• Slow vpostgres-repl service startup on replica node.
• AWS dashboard issues - s3 buckets not showing object count.
• Adding Log Analysis widget on dashboard takes forever.
• Add wal_keep_size setting to vROps 8.10+ repl db postgresql.conf.
• CAS MP - Manual discovery from inventory fails with error "Discovery result is null for adapter kind CAS Adapter".
• vRealize Operations upgrade to 8.12.x failure at OS upgrade stage.
• JS error after details button click.
• User cannot access public shared Dashboard after upgrading to 8.12, when LI adapter instance exists.
• [Launchpad] Some documentation links redirect to the wrong pages.
• Unable to see the "Image" type views in the "Output Data" section in the described case.
• [GCVE Adapter] Component end date is incorrect when created using the statement bill.
• IndexOutOfBoundsException is raised when the VC adapter receives fewer data points than requested.
• Linux Bootstrap is failing because of urllib3 upgradation.

The following CVEs have been resolved as of version 8.12 Hot Fix 1:

Component	CVE
gson	CVE-2022-25647
linux_kernel	CVE-2023-1829
	CVE-2018-16880
	CVE-2023-1281
jettison	CVE-2023-1436
hibernate-validator	CVE-2020-10693
	CVE-2019-10219
spring-core	CVE-2023-20860
snakeyaml	CVE-2022-38749
	CVE-2022-1471
	CVE-2022-38750
	CVE-2022-25857
	CVE-2022-38752
	CVE-2022-38751
	CVE-2022-41854
rpm	CVE-2021-20271
vim	CVE-2022-3520
	CVE-2022-3324
	CVE-2022-2819
	CVE-2022-4292
	CVE-2022-2946
	CVE-2022-3591

VMware Aria Operations 8.12.x

VMware Aria Operations 8.12 Hot Fix 1 can be applied to any 8.12 environment.
Note: Upgrading from older versions directly to this Hot Fix is not supported.  You must upgrade to 8.12 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 1 PAK file from the VMware Patch Portal.

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.