This article covers the fixes made in VMware Aria Operations 8.14.1 from previous versions.

Important notice regarding Remote Collectors:
Cloud proxies have been established as a long-term solution for data collection.  In future releases, the introduction of new features will be exclusively limited to cloud proxies, if relevant.  The announcement regarding the expiration of support for Remote Collectors and the prohibition of deploying new remote Collectors has already been added in the previous 8.10 Release notes and accompanying documentation.

VMware Aria Operations 8.14.x will be the last release to provide support for Remote Collectors.  In the next on-premises release, upgrades will not be allowed if there are Remote Collectors in use.  To upgrade to the next version or a later one, it is imperative to replace all Remote Collectors with cloud proxies.
As a recommendation, the following steps are proposed:

• If you are using a collector group, add new cloud proxies to it and remove the Remote Collectors.
• If you are not already using a collector group, create a new collector group and deploy cloud proxies into it.  Reassign all adapter instances that were previously associated with Remote Collectors to the collector groups and remove the Remote Collectors.

The following issues have been resolved as of vRealize Operations 8.14.1:

• NPC Add-on upgrades product edition.
• [Rebranding] The product name is incorrect in the "Add Software Update" pop up.
• [What If] Add Host scenario when clicking "Select" Server displays no results.
• Cost calculation is failing for K8s datacenters.
• Optimizing vCenter Adapter's Symptom Querying.
• [VCF Compliance] Duplicate Symptom Definition for v4.4 Alert Definition.
• CPU|vCPUs Allocated on all Consumers metric considers also VM Templates.
• Virtual Disk:<disk_id>|Provisioning Type property is not reported correctly on Virtual Machine.
• CP's upgrade failed.
• Improving Data Collection Through Decoupling the Execution of fillInHardwareSensorEventsMap Function.
• TCP check availability metric is getting inconsistent data.
• Issue with VMC Cloud Account export/import.
• "Internal Error" when navigating to a resource summary page.
• OpenManage Management Pack fails at validation phase.
• The appliance becomes unresponsive during Aria Operations upgrade to 8.14.
• Issues with k8s namespace cost and k8s cluster cost.
• [What if analysis] Add VM and Remove VM scenario shows cost as 0 for both traditional and hyperconverged scenarios.
• Need to reconfigure "/var/log/messages" file rotation.
• The allocation costs are not published for private cloud clusters when allocation model is enabled.
• Handle unhandled exceptions seen in AppOSAdapter.
• Gemfire logs show that the threads are stuck.
• [Notifications] Notification is sent regardless of the "Status" defined in the "Define Criteria" tab.

The following CVEs have been resolved as of vRealize Operations 8.14.1:

Component Name	CVE
apache	CVE-2023-31122
	CVE-2023-43622
	CVE-2023-45802
bind	CVE-2023-3341
cri-o	CVE-2022-3466
	CVE-2022-4318
gawk	CVE-2023-4156
	CVE-2023-3164
glibc	CVE-2023-4527
	CVE-2023-4911
	CVE-2015-20109
	CVE-2023-4806
golang-runtime	CVE-2023-45283
httpd	CVE-2023-31122
libx11	CVE-2023-43785
	CVE-2023-43786
	CVE-2023-43787
linux_kernel
	CVE-2020-12363
	CVE-2022-4696
	CVE-2023-0469
	CVE-2023-39189
	CVE-2023-39192
	CVE-2023-39193
	CVE-2023-4244
	CVE-2023-42752
	CVE-2023-42753
	CVE-2023-42754
	CVE-2023-42755
	CVE-2023-45871
	CVE-2023-4610
	CVE-2023-4623
	CVE-2023-4921
	CVE-2023-5197
	CVE-2023-6176
nghttp2	CVE-2023-35945
open-vm-tools	CVE-2023-34058
	CVE-2023-34059
org.apache.xmlgraphics:batik-xml	CVE-2022-44729
	CVE-2022-44730
org.bitbucket.b_c:jose4j	CVE-2023-31582
vim	CVE-2023-5344
	CVE-2023-5441
	CVE-2023-5535

VMware Aria Operations 8.14.x

vRealize Operations 8.14.1 can be applied to any 8.6.x - 8.14.x environment.

It is recommended to take snapshots following How to take a Snapshot of vRealize Operations before upgrading.

1. Download the vRealize Operations 8.14.1 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.

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.

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.