vRealize Operations 8.10.2
Article ID: 337367
Updated On:
Products
VMware Aria Suite
Issue/Introduction
This article covers the fixes made in vRealize Operations 8.10.2 from previous versions.
The following issues have been resolved as of vRealize Operations 8.10.2:
The following CVEs have been resolved as of vRealize Operations 8.10.2:
The following issues have been resolved as of vRealize Operations 8.10.2:
- [vSphere Hardening Compliance] Alarms to be updated for specific network portgroup.
- Possible incorrect product name in \projects\mps\vmc\conf\resources\resources.properties.
- After Upgrade to 8.10, VMs showing as non compliant for CIS.
- ARC operations are failing as the port 4505/4506 is not reachable.
- [Internal Auth] Enable/Disable basic authentication request validation fails.
- Failed to install telegraf agent manually/UI on windows-korean language.
- Pre-upgrade assessment tool should include a check to see if all Telegraf endpoints have been migrated to Cloud Proxy from ARC prior to upgrade to version 8.10 and above from version 8.6.
- Upgrade through vRLCM gives error LCMVROPSYSTEM25008 at stage 11 while trying to upgrade from version 8.6.4 to 8.10.
- Custom time pop menu cannot display completely in share dashboard.
- Issues for some objects types in Object Browser > Compliance tab of the corresponding objects.
- Resources with custom data center kind being deleted from the system because of improper set of orphan time.
- The casa token server is unable to load cluster_key.pem when it is PKCS#1 formatted.
The following CVEs have been resolved as of vRealize Operations 8.10.2:
| Component Name | CVE |
|---|---|
| bcel | CVE-2022-42920 |
| glib | CVE-2021-3800 |
| golang-runtime | CVE-2022-2879 |
| CVE-2022-41716 | |
| CVE-2022-2880 | |
| CVE-2022-41715 | |
| CVE-2022-32190 | |
| CVE-2022-27664 | |
| CVE-2022-1705 | |
| CVE-2022-1962 | |
| CVE-2022-28131 | |
| CVE-2022-29804 | |
| CVE-2022-30580 | |
| CVE-2022-30629 | |
| CVE-2022-30630 | |
| CVE-2022-30631 | |
| CVE-2022-30632 | |
| CVE-2022-30633 | |
| CVE-2022-30635 | |
| CVE-2022-32148 | |
| CVE-2022-32189 | |
| CVE-2022-30634 | |
| CVE-2022-29526 | |
| grub2 | CVE-2022-3775 |
| CVE-2022-2601 | |
| jettison | CVE-2022-45685 |
| CVE-2022-45693 | |
| json-smart | CVE-2021-31684 |
| CVE-2021-27568 | |
| libksba | CVE-2022-47629 |
| libxml2 | CVE-2022-40304 |
| CVE-2022-40303 | |
| CVE-2016-3709 | |
| CVE-2022-29824 | |
| CVE-2022-23308 | |
| CVE-2021-3541 | |
| CVE-2021-3517 | |
| CVE-2021-3537 | |
| CVE-2021-3518 | |
| linux_kernel | CVE-2022-3628 |
| CVE-2022-4378 | |
| CVE-2022-20568 | |
| CVE-2022-3643 | |
| CVE-2022-42896 | |
| CVE-2022-42895 | |
| CVE-2022-3564 | |
| CVE-2022-41222 | |
| CVE-2022-1508 | |
| CVE-2022-21499 | |
| netty | CVE-2022-41915 |
| CVE-2022-41881 | |
| CVE-2021-43797 | |
| CVE-2022-24823 | |
| velocity | CVE-2020-13936 |
| wget | CVE-2021-31879 |
Environment
VMware vRealize Operations 8.10.x
Resolution
vRealize Operations 8.10.2 can be applied to any 8.6.x - 8.10.x environment.
It is recommended to take snapshots following How to take a Snapshot of vRealize Operations before upgrading.
- Download the vRealize Operations 8.10.2 upgrade PAK file from Broadcom Support Portal.
- Log in to the master node vRealize Operations Administrator interface of your cluster at https://master-node-FQDN-or-IP-address/admin.
- Click Software Update in the left panel.
- Click Install a Software Update in the main panel.
- Follow the steps in the wizard to locate and install your PAK file.
- Install the product update PAK file.
Wait for the software update to complete. When it does, the Administrator interface logs you out. - 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.
- 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.
- 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.
Feedback
Yes
No
Powered by
