vRealize Operations 8.5
search cancel

vRealize Operations 8.5

book

Article ID: 337324

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

This article covers the fixes made in vRealize Operations 8.5 from previous versions.

The following issues have been resolved as of vRealize Operations 8.5:
  • Review REST APIs enabling alert definitions in policies.
  • API Doesn't allow to PUT /api/adapters the output from the get call.
  • [Swagger] Fix some linting errors in OpenAPI Specification.
  • Analytics and Collector services have been restarted by oom-killer.
  • Log partition on node steadily filling up with suite-api access logs.
  • [VMC Cost Allocation] Discrepancy in cost between bills and vRealize Operations.
  • Views: Inconsistency in chosen and written time range.
  • Issues regarding dark color scheme.
  • [Proxy RC] Once cloud proxy can upload the support bundle with other cloud proxy UUID.
  • Revisit exception handling in REST API.
  • Cluster Base rates calculation does not consider CPU, memory and storage utilization values for hosts in not responding state.
  • [what-if] Add FTT-3 support by upgrading vSAN Sizer jar.
  • Threshold is specified twice in heatmap widget configuration in 'CMA - VCF Capacity' dashboard.
  • Updating adapter instance credentials, the referenced credentials should be updated automatically.
  • Cassandra OOM crash and heap files rotation missing.
  • Alerts which Alert definition contain \ backslash sign are not being sent to SNOW.
  • No pagination for Cloud Proxies page.
  • Unable to view additional user groups if the count is above 25 when sharing dashboards.
  • Show Certificate count in Certificates page.
  • Failed to create error result of type ResourceIconsResult, none of the expected constructors are found.
  • Need an optimization to add label based filtering for counters in vSAN perf API query specs.
  • The vSAN term “slack space” should no longer be used in vSAN adapter and vRealize Operations in general.
  • Alert definitions disappear from UI when deleting all from the last page.
  • Fix repetition logic of validateCredentialsInGuest API when 'The operation is not allowed in the current state.' exception is thrown.
  • Remove obsolete migrationAdmin user.
  • Billing Objects|Object count metric is not accurate.
  • Adding a Node Fails on Offline Cluster.
  • Add customization support for "World" groups description.
  • updateLogConfigurations API not checking the root log level deferens and max log size.
  • No audit logging when archived user, which has an already created dashboard, is permanently deleted from the page  Orphaned Content.
  • NullPointerException in Controller Server getResources call.
  • [VMC Cost Allocation] Issue when a Region has both i3 and i3en hosts.
  • NullPointerException in ReportRenderer while generating reports.
  • "Number of  CPU metric" is not showing actual number of virtual CPUs.
  • IllegalArgumentException in CalculateDT - bound must be positive.
  • Spelling Typos in Help Text for Friendly Name in Cloud Proxy OVA Template.
  • Need to provide an ability add job and get report for Cloud Zone object types.
  • Empty widget when WLP can't calculate Cluster utilization balancing.
  • Remove the property Summary|Configuration|Appliance.
  • Showing incorrect icons in the "Topology Graph" widget.
  • Reports: Report retains original Column Order.
  • Warning message in Instance State config window needs to be removed.
  • CaSA doLocalRoleStatusRequest function shouldn't update cashed roles document.
  • Region location is not localized in SDDC summary details page.
  • View configuration cannot be saved correct if "breakdown" label customized and browser locale is non-English.
  • Deleted VM's price/cost metrics on Host, Cluster, Datacenter should be removed from policies.
  • Manual changes in VC adapter property file need to be persisted after upgrade.
  • Remove the obsolete "Import Data" Permission from vRealize Operations.
  • CSP Users duplicated in case of CSP AD integration.
  • Email must be supported as username in the imported vIDM user in vRealize Operations.
  • Email notification that uses old template sends a duplicate email.
  • "Manage Cloud Proxies" permission for "Administrator" Role in upgraded setups is missing.
  • After upgrade from 8.3 to 8.4 GA build product UI page is blank in eso-vRealize Operations.eng.vmware.com.
  • Arrow icon is missing.
  • Not receiving ServiceNow notifications for new alerts in vRealize Operations after upgrading to 8.3 HF 1.
  • Reports showing "no data" after upgrade to 8.4.
  • VMC and vRealize Operations one-touch integration vs traditional integration.
  • storagePath:*  metric keys should not be cached in adapter.
  • Provide REST API for SRE to remove cloud proxy from vRealize Operations.
  • vRealize Operations Manager Unauthorized Logfile read vulnerability.
  • vRealize Operations Manager Unauthorized API access to add node to cluster.
  • Fail to force import dashboard on vRealize Operations 8.2 and 8.3.
  • Exported pdf report showing no data if the "dashboard" that is in report contain "text widget".
  • When creating a new message event based symptom definition, the spaces are not allowed in the definition name.
  • Missing Advanced Settings of VRNI MP after upgrading from 8.1 to 8.3.
  • Object cache cannot be loaded due wrong symptom reference.
  • [pDRS] Need to change the "Summary|pdrsCapable" property from dynamic to static for vCenter Server object type.
  • Non-Admin User Sees Alert Banner for Expired Certificates.
  • Views for VM rightsizing contain VM that do not need adjustment.
  • From ARC to CP migration script execution failed for VMC environment due to VMC-VC IP is not resolvable from ARC.
  • Object Count in Billing Audit Report to Exclude "Non-Collecting" Objects.
  • OnPrem: Bulk export must export all the content for all the administrators.
  • Duplicate email is sent when old template is present.
  • Add support for vRCU add-on license.
  • Webhook is not creating valid JSON message when sending the alert.
  • ${ADAPTER_INSTANCE} returns wrong value in alert notification payload.
  • Cluster Capacity bar chart shows incorrect visualization of its values in case of HA and Buffer in Object Detail page.
  • CP has failed to connect to the cluster after the upgrade.
  • User doesn't have access to create "Recommendation", but the "Create New Recommendation" button active for the user.
  • Server cost change does not work in per DC mode.
  • Two NSX-T Adapters are not collecting after upgrading to vRealize Operations 8.2.
  • [VMC Adapter] Change not Configured  SDDCs status from "Activated" to "Not Configured".
  • Updating adapter instance credentials, the referenced credentials should be updated automatically. (Second reported issue of this type)
  • Two strings connected in file \projects\mps\vcenter-solution\content\dashboards\vSphereDashboards\resources\resources.properties.
  • Reword camel words in file \projects\mps\azure\conf\resources\resources.properties.
  • "Custom Group" traversal spec ignores resources with "Tag" resourceKind type.
  • Alert, which will fire when there is no space left on datastore, has an "info" level rather than "critical".
  • EPOPs 8.2,vRealize Operations 8.3 | HTTP Check does not work when using credentials.
  • [Policy] If custom profile is created and added to object, further changes to the policy causes an error.
  • View Request of SDDC MP views is timed out.
  • The interactions are not working for the cloned dashboards.
  • CPU|Allocation|Usable Capacity after HA and Buffer (vCPUs) metric missing HA portion.
  • Stored XSS when configuring adapter Instances.
  • Discrepancies between billing and information displayed in TA  2.6 UI and VREALIZE OPERATIONS 8.4  Ui.
  • ARC to CP migration script rerun is failing with error message if passed CP value is FQDN instead of migrating remained VMs.
  • GCP Adapter for VREALIZE OPERATIONS not collecting data.

The following CVEs have been resolved as of vRealize Operations 8.5:
Component NameCVE
apacheCVE-2021-32785
CVE-2020-13950
CVE-2021-26690
CVE-2020-35452
CVE-2021-26691
bindCVE-2021-25215
CVE-2021-25216
cairoCVE-2020-35492
cryptographyCVE-2020-36242
curlCVE-2021-22901
expatCVE-2019-15903
CVE-2018-20843
glibCVE-2020-35457
CVE-2021-27218
CVE-2021-27219
gnutlsCVE-2021-20231
CVE-2021-20232
jdomCVE-2021-33813
libgcryptCVE-2021-33560
libxml2CVE-2021-3518
CVE-2021-3517
linux_kernelCVE-2021-27364
CVE-2021-32399
CVE-2020-36313
CVE-2021-0512
CVE-2021-22555
CVE-2021-27365
CVE-2021-33033
CVE-2021-33034
CVE-2021-3444
CVE-2021-3483
CVE-2020-25672
CVE-2021-3506
CVE-2021-23133
CVE-2019-25044
CVE-2020-25220
CVE-2020-25670
CVE-2020-25671
CVE-2021-28660
CVE-2021-29154
CVE-2021-3612
nettleCVE-2021-3580
CVE-2021-20305
opensslCVE-2019-1543
postgresqlCVE-2021-32027
CVE-2019-10128
CVE-2019-10127
runcCVE-2021-30465
spring-security-coreCVE-2021-22112
spring-security-webCVE-2021-22112
urllib3CVE-2019-11324
xstreamCVE-2021-29505
zeromqCVE-2021-20235


Environment

VMware vRealize Operations 8.5.x

Resolution

vRealize Operations 8.5 can be applied to any customer's 7.5 - 8.4 environment.

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

  1. Download the vRealize Operations 8.5 upgrade PAK file from SolutionFiles - Support Portal - Broadcom support portal
  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.
  1. 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.
  1. Click Software Update to check that the update is done.
    A message indicating that the update completed successfully appears in the main pane.
Powered by Wolken Software