This site will be decommissioned on December 31st 2024. After that date content will be available at techdocs.broadcom.com.

 

vRealize Operations 8.10 | 11 OCT 2022

Check for additions and updates to these release notes.

Build Details

VMware vRealize Operations 8.10 | 2022 | Build 20570121

VMware vRealize Operations Upgrade PAK | 2022 | Build 20570120

Note:This upgrade .pak file includes the OS upgrade files from Photon to Photon, the vApp upgrade files, and Cloud Appliance upgrade files.

VMware vRealize Operations 8.10 Pre-Upgrade Assessment Tool | 2022 | Build 20579730

VMware vRealize Operations Cloud Appliance (vRealize Operations Cloud Proxy) 8.10 | 2022 | Build 20569886

Check frequently for additions and updates to these release notes.

What's New

Read about the new and enhanced features in this release under Key Features and Capabilities.

Product Support Notice

vRealize Application Remote Collector

vRealize Application Remote Collector is not supported from vRealize Operations 8.10 and above. Migrate all Telegraf end points to cloud proxy before upgrading to vRealize Operations 8.10 and above. For information about migrating from vRealize Application Remote Collector to cloud proxy, see KB 83059.

Key Features and Capabilities

Update of OpenJDK 8 to OpenJDK 11

Note: As a result of the OpenJDK update, some management packs might not be compatible with JDK11 and would require an upgrade to a JDK11 compatible version. Contact the vendor to confirm if the management pack is compatible with vRealize Operations 8.10. See KB 89675 for more details.

Core Based Licensing

In this release, Core Based Licensing is available under vRealize Cloud Universal and vRealize Suite. For more information, see: Support for vRealize Cloud Universal ‘core’ based offering.

vSAN ESA Support in vRealize Operations

vSAN Adapter Enhancements

SPBM API Support Added

In addition to the above change two new metrics "Usage Without Overhead (GB)" and "vSAN Overhead(GB)" have been introduced.  

Remote Collectors

In this release, remote collectors will be upgraded to a lighter version of cloud proxy, and will be displayed in the cloud proxy sections on the admin and the client interfaces. The lighter version of cloud proxy will have all the capabilities of a cloud proxy except data persistence and application monitoring. Their type will still be Remote Collector, and the same remote collector sizing guidelines will continue to apply. If there is a need to redeploy a collector, a cloud proxy needs to be deployed. For more details, see About vRealize Operations Remote Collector Nodes.

vRealize Operations Cloud Proxy Enhancements

  • vRealize Operations Cloud Proxy Resiliency

    • vRealize Operations cloud proxy now provides enhanced resiliency to handle network interruptions during upgrade.

    • Improved connection load management between vRealize Operations cloud proxy and the cloud to minimize drops in environments with high load.

  • vRealize Operations Cloud Proxy Troubleshooting

    • Users would now see error messages related to incorrect OTK (used while deploying the cloud proxy) in the logs.

    • vRealize Operations customers would now be automatically notified to manually upgrade Cloud Proxy in case of upgrade failures due to network interruptions.

    • Users can now troubleshoot cloud proxy connection and upgrade related issues by referring to the updated Cloud Proxy Troubleshooting topic.

    • Cloud Proxy FAQ topic to help with connection, sizing, migration and high availability related queries.

    • vRealize Operations cloud proxy now checks and alerts for upgrade failures due to space constraints. The proactive alert will help with quick remediation to minimize any collection loss. 

    • vRealize Operations cloud proxy support bundle now captures system variable, service statuses and other configurations for faster troubleshooting.

  • Cloud Proxy troubleshooting CLI

    • A new CLI option -d now helps diagnose frequently occurring issues relating to installation, connection, network and services.

    • It highlights the issue, and provides remediation steps, for faster troubleshooting.

      For more information, see the topic, Using the Cloud Proxy Command Line Interface.

  • Cloud Proxy certificate management

    • Cloud Proxy now allows addition of multiple certificates or a certificate group while deployment.

    • Additional certificates may be added to a Cloud Proxy by adding vApp option properties using the key class ID cprc_ca. This helps segregate the various certificates for better management.

    • A new CLI option -cs  now shows the status of all certificates added to a Cloud Proxy, clearly highlighting any incorrectly configured certificate.

    • For more information, see the following topics:

      Configuring Cloud Proxies in VMware Cloud

      KB 83698

      Using the Cloud Proxy Command-Line Interface

  • Cloud Proxy upgrade enhancement

    • To ensure optimum use of network bandwidth, Cloud Proxy upgrades would now happen sequentially, starting with 10, and then rolling as CPs get upgraded.

    • For more information, see the topic, Upgrading Cloud Proxy.

  • Data Persistence for Cloud Proxy

    Cloud Proxy now allows for persistence of data to ensure service continuity in case of network interruptions.

  • For more information, see the following topics:

  • Fixes

    • Log rotation fixes for efficient partition management in cloud proxy VM.

    • Deletion of cloud proxy now removes any deleted local users from the orphan content section.

 vRealize Operations Retention Policy Update

  • Data Retention policy configured will now also apply to Historical Data (Objects, Metrics, Properties and Reports) retained in the system after deleting Cloud Accounts. For more information, see List of Global Settings.

Search support in the administration page

  • vRealize Operations now provides a search box in the administration page to search for an administration item.

Advanced workload placement

  • vRealize Operations provides workload placement recommendations for vRealize Automation Manager. vRealize Operations identifies the best cluster for deployment among several cloud zone clusters. 

  • The current algorithm takes into account the cluster utilization based on demand model only. The demand across all clusters in a given cloud zone is evaluated against the deployment request in order to recommend the most suitable cluster. However, there are use cases that needs placement decisions to also consider allocation model. This feature leverages the over commit ratios in addition to demand model to make placement recommendations.

Alerts enhancements

  • Actions and Recommendations sections now provide a detail view, along with a navigation link to the corresponding recommendations, and alert definitions respectively. This will help improve search and discovery of relevant actions, recommendations and alerts.

Access control enhancements

  • A new configuration element, “Scope,” allows you to control the access to objects in a template format in conjunction with Roles.

  • The User Interface of the Add and Edit operation is changed from multi-page to single-page design. This allows you to review and edit the configuration easily. For more information, see: Access Control in vRealize Operations.

Filter enhancement

  • vRealize Operations now provides users the ability to perform combinational search through the various filters available in the product, to simplify discovery. Users can now use "\", ":", "," and whitespace to provide more precise filter.

  • vRealize Operations now provides users the ability to provide string representation of the available filters in the form of key:value pairs, to simplify search and discovery of content.

New properties added for RDM Disk in virtual machines

  • Support for RDM has been added in vRealize Operations in this release. You can now see the properties of RDM Disks in vRealize Operations.

  • Properties for Multi Disk Sharing and SCSI Bus Sharing have been added. For more information, see Virtual Machine Properties.

Simple alerts

  • Users now have the ability to create a simple alert without the need to create an associated symptom definition. This can be done by using metrics and by creating in-line conditions directly from metric charts eventually applying the alert to objects of the same type within the applicable policy.

Automation central improvements

  • New Monthly recurrence for the jobs. Schedule a job for multiple days in a multiple months at once. Flexible Date and Day in a week selection.

  • Set start time in 5 minutes interval with default the closest to your local time.

  • Simplify page design.

  • For more information, see the topic, Create Job from Automation Central.

Application discovery based on rules

For more information, see the topic, Discovered Rule-Based Applications.

  • With a single easy to create rule, you can discover multiple applications.

  • Rules can be defined based on tags, properties, and object names.

  • You may control the scope of objects within which applications are discovered in 'Environment->Applications->Manage Applications' page. You could control the discovery at the level of vCenter, Cluster compute resource, Host system etc.

NSX-T using IPv6

  • vRealize Operations can now integrate with NSX-T endpoint using an IPv6 address.

For more information, see the topic, Configuring the NSX-T Adapter.

Application discovery based on services

  • You may control the scope of objects within which applications are discovered in 'Environment->Applications->Manage Applications' page. You could control the discovery at the level of vCenter, Cluster compute resource, Host system etc.

  • Previously, discovery would happen at the vCenter level by default.

  • For all new application definitions, you are now needed to specify the scope as a mandatory step after creating the application definition.

  • For all existing application definitions, discovery will continue at vCenter level post upgrade.

New Metrics and properties to expand Cloud Management capabilities and visibility

  • Three new VM metrics IOPS per GB, Peak Network Packet per second and Peak Guest OS Page-out rate have been introduced in this release.

  • In addition to the above change New Properties for VM, Host, Cluster, Datastore, Datastore Cluster, Distributed Port Group and Distributed Switch have been added as well. See the updated documentation on vCenter Properties to get exact details in this regard.

For more information, see the topic, Metric, Property, and Alert Definitions.

Super Metrics

  • Workflow is redesigned to simplify the creation of super metrics.

  • Formula typing experience is improved.

  • 'This' option on the UI is moved to the formula editor.

  • The object selection pane in the 'Legacy' tab is deprecated.

For more information, see the topic, Create a Super Metric.

VCF cloud account

  • You can configure VCF cloud account to auto discover domains and underlying adapters along with their credentials.

  • Introducing VCF traversal spec, summary pages and OOTB dashboards. 

For more information, see the topic, VMware Cloud Foundation.

VMware Cloud on Dell EMC cloud account

For more information, see the topic, VMware Cloud on Dell EMC.

  • Manage and monitor VMware cloud on Dell EMC with a simplified and dedicated cloud account.

  • Discover VMware cloud on Dell EMC SDDCs and configure the adapters to monitor vCenter, vSAN and NSX-T.

  • Traverse VMware cloud on Dell EMC objects, view summary pages, configuration maximums and get alerts for configuration maximums.

  • Plan workload migration using What-if migration scenario to migrate workload to VMware cloud on Dell EMC.

  • Run compliance analysis for virtual machines against various benchmarks, review cost based on rate card costing.

  • Rightsize workloads.

Native Public Cloud

Export views to external tools for reporting

  • vRealize Operations now allows exporting views via API, using the view definition ID.

  • This capability can be used to export views to tools such as MS Power BI and Tableau for reporting purposes.

For more information, see the topic, Share a View.

View Enhancements

  • Experience enhancement to provide flexible preview and intuitive flow.

  • A sample preview source is now selected by default for faster feedback on presentation of the view.

  • Last selected preview source is shown in history to help preserve view configuration.

Note: The capability to add and edit Views and Dashboards directly from the Report template has been deprecated in vRealize Operations 8.10.

For more information, see the following topics:

Capacity management

  • Ability to reserve resources for upcoming projects using 'commit', in tandem with what-if analysis for capacity planning.

  • View results of what-if analysis based on allocation model. 

  • Ability to specify business hours for capacity calculations.

For more information, see the following topics:

Configuration files page redesign

  • Users can now organize their files into custom folders and perform actions such as edit, add, and delete folders, thereby giving them more flexibility. The user experience has also been made consistent to other product areas.

For more information, see the following topics:

Product walk throughs through in-app guides

  • In-app guides are multi-step guided walk throughs that are designed to help the users complete a workflow within vRealize Operations. These guides help users to complete the various core workflows. The guides provide navigation to the user through the product pages providing valuable information to quickly complete the task. The in-app guides can be accessed via the guide launcher icon. Appropriate guides are shown based on the user's role.

End Point Operations Adapters

End Point Operations adapters are automatically removed when you upgrade vRealize Operations to 8.10.

Metrics and Properties Modifications

The following KB article describes all the metrics and properties that have been modified in vRealize Operations 8.10:

Metrics added in vRealize Operations 8.10

Updated Management Packs 

The following VMware Management Pack has been updated for vRealize Operations 8.10:

  • vRealize Operations Management Pack for Horizon 2.2

  • vRealize Operations Management Pack for VMware Cloud Director 8.10

  • VMware vRealize Operations Management Pack for SDDC 8.10

See Management Packs for vRealize Operations Documentation for more information. Refer to the VMware Product Interoperability Matrix for all VMware Management Packs supported with vRealize Operations 8.10.  The 3rd party authored Management Packs that are supported with 8.3 are listed in the VMware Compatibility Guide.

Instanced Metrics

Instanced metrics are deactivated by default after deploying or upgrading to vRealize Operations 8.2 or later, and after importing a policy from older versions. To re-activate instanced metrics in vRealize Operations 8.2 or later, see KB 81119.

Basic Authentication

Basic authentication using the REST API is deprecated and deactivated in vRealize Operations 8.10 fresh deployments by default. Instances that have been upgraded to vRealize Operations 8.10, will inherit the same properties before the upgrade. It is recommended that you use token-based authentication instead. If you still need to activate or deactivate basic authentication, see KB 77271.

Active Directory Authentication Sources

Logging in to vRealize Operations with a short name will be successful only if the user name's domain suffix matches the domain name specified in the Base DN option. Otherwise, the full user name with the domain suffix is required during login. For more information, see KB 68131

System Requirements

Review this section before you install or update vRealize Operations.

Sizing and Scaling

The CPU, memory, and disk requirements that meet the needs of a particular environment depend on the number and type of objects in your environment and data collected. This includes the number and type of adapters installed, the use of HA (High Availability) and CA (Continuous Availability), the duration of data retention, and the quantity of specific data points of interest. VMware updates Knowledge Base article 2093783 with the most current information about sizing and scaling. The Knowledge Base article includes overall maximums and spreadsheet calculations that provide a recommendation based on the number of objects and metrics you expect to monitor.

Deployment Formats

You can deploy vRealize Operations 8.10 with VMware virtual appliance.

If you are deploying a vRealize Operations virtual appliance and vRealize Operations Cloud Appliance (cloud proxy), use a VMware vSphere Client to connect to a VMware vCenter Server, and deploy the virtual appliance through the vCenter Server instance. The vRealize Operations virtual appliance and vRealize Operations Cloud Appliance (cloud proxy) must be deployed on hosts that are:

  • ESX/ESXi 6.5 Update 1 or later and managed by VMware vCenter Server 6.5 or later.

  • If you have vRealize Operations virtual appliance deployed on ESXi 6.0 or older hosts, you must first upgrade vCenter Server and ESXi to version 6.5 Update 1 or later, and then upgrade to vRealize Operations 8.10.

Hardware Versions, Cipher Suites and Protocols, and Log4j

Hardware Versions

The minimum hardware version required for vRealize Operations 8.x releases is version 11. If your vRealize Operations virtual appliance had a hardware version earlier than 11, you must first upgrade to hardware version 11 on vRealize Operations virtual appliance and then upgrade to vRealize Operations 8.10.

Cipher Suites and Protocols

For information about cipher suite lists and relevant protocols, see Cipher Suites and Protocols.

Log4j version is at 2.17.2.

VMware Product Compatibility

VMware Product Compatibility

Note: The VMware Product Interoperability Matrix provides details about the compatibility of vRealize Operations with VMware products.

Note: For FIPS mode compatibility details, see the footnotes in the interoperability matrix. The product will not work in FIPS mode if there are footnotes that state that it will not work in FIPS mode.

Solutions and Browser Support

Solutions Support

In addition to the VMware solutions (vSphere, vRealize Log Insight, vSAN, Service Discovery, NSX-T, and many more), see the VMware Marketplace for many more solutions. These solutions work with Virtual Appliance single or multiple nodes.

Browser Support

This vRealize Operations release supports all current Web browsers, although only the following browsers were tested with this release:

  • Google Chrome: Version 104 and 105

  • Mozilla Firefox: Version 104

  • Microsoft Edge: Version 104 and 105

  • Safari: 15 and 16

Note: Support for Internet Explorer has been dropped from vRealize Operations 8.4 onwards.

SDDC Compliance

To ensure compliance of your vSphere, VMware Cloud on AWS, and vSAN 7.0, 6.7, and 6.5 objects, and also NSX-T 2.3, 2.4, and 2.5, and NSX-V 6.3.x and 6.4.x objects, vRealize Operations 8.10 includes compliance alerts for VMware vSphere Security Configuration Guides versions 6.7 Update 1 and 6.5. These security configuration guide alerts are based on the corresponding object types. Some of the alerts and symptoms are available only for backward compatibility with older versions of vSphere, even though the current release supports the latest vSphere Security Configuration Guide 6.7 Update 1.

Note: Compliance rules will work on vSphere 7.0 objects as well. However, those rules are based on vSphere Security Configuration Guide 6.7 Update 1.

Installing and Upgrading vRealize Operations

Upgrading to vRealize Operations 8.10, resets out-of-the-box content as part of the software upgrade process. This implies that the user modifications made to default content such as alert definitions, symptom definitions, recommendations, policies, views, dashboards, widgets, and reports are overwritten. You need to clone or backup the content before you upgrade to vRealize Operations 8.10.

Notes:

  • To see the supported direct upgrade path, refer to the Product Interoperability Matrix.

  • To upgrade from vRealize Operations 8.4.x or 8.5.x with cloud proxy connected, to vRealize Operations 8.10, upgrade to vRealize Operations 8.6 first and then upgrade to vRealize Operations 8.10.

  • While upgrading to vRealize Operations 8.10, the expected size of the /dev/sda for Photon OS is 20 GB (hard disk 1). For information about this requirement, see KB 75298.

  • It is always recommended to run the Pre-Upgrade Assessment tool before an upgrade. A pre-upgrade assessment report that is generated will provide you with the recommended replacements. This tool provides you with an impact analysis following the reduction of metrics in various versions of the product. For more details on using the Pre-Upgrade Assessment Tool, see KB 89588.

Refer to the vRealize Operations Upgrade Center that has information about upgrading vRealize Operations. Refer to the VMware Lifecycle Product Matrix for information about supported versions of vRealize Operations.

vRealize Suite Lifecycle Manager 8.10 supports the installation of vRealize Operations 8.10. For more information, see VMware vRealize Suite Lifecycle Manager 8.10.x Release Notes.

The vRealize Operations Information Center has detailed information about installation and software updates.

Refer to the vRealize Operations vApp Deployment and Configuration Guide that provides guidance for a vRealize Operations virtual appliance, before you install or update vRealize Operations.

Deploy vSphere with Operations Management (any edition) and vRealize Operations Standard together in one deployment.

Deploy vCloud Suite/vRealize Suite Standard, Advanced, or Enterprise and vRealize Operations Advanced or Enterprise edition together in one deployment.

Note: You can also install vRealize Operations by using vRealize Suite Lifecycle Manager. For more information, see the vRealize Suite Lifecycle Manager Installation, Upgrade, and Management Guide.

Resolved Issues

For details on resolved issues, see KB 89587.

Known Issues

Installation and Upgrade Issues

  • vRealize Operations upgrade from 8.6.4 to 8.10 fails

    vRealize Operations upgrade from 8.6.4 to 8.10 fails due to a missing Cassandra table vmwarecloudonawscomputationratio.

    Workaround: See KB 90606 or upgrade to vRealize Operations 8.10.2.

  • Upgrade to vRealize Operations 8.10 will impact some management packs

    When you upgrade to vRealize Operations 8.10, some management packs might not be compatible with JDK11 and would require an upgrade to a JDK11 compatible version. Contact the vendor to confirm if the management pack is compatible with vRealize Operations 8.10.

    Workaround: See KB 89675 for more details.

  • The PAK file upload process is slower in vRealize Operations 8.10

    The vRealize Operations 8.10 upgrade PAK file may take longer to upload and may sometimes not complete uploading if you are using Firefox as a browser through a high latency network.

    Workaround: Use another supported browser to upload the PAK file and start upgrading to vRealize Operations 8.10.

  • After you upgrade vRealize Operations from 8.4 to a later release, content upgrade and agent management actions fail

    After you upgrade vRealize Operations from a previous release, content upgrade and agent management actions fail on vRealize Operations on-prem and vRealize Operations Cloud when you also upgrade cloud proxy.

    Workaround:

    Complete the following steps:

    1. SSH to the Cloud Proxy VM.

    2. Run the following command: /rpm-content/ucp/subsequentboot.sh

    You can view the log from the following location: /opt/vmware/var/log/ucp-subsequentboot

  • Upgrade might fail if any of the nodes are running on VMs with US/Pacific-New timezone

    PostgreSQL database systems no longer support the US/Pacific-New timezone, which was just an alias for America/Los_Angeles timezone. If any of the vRealize Operations nodes are running on VMs with US/Pacific-New timezone, upgrade might fail.

    Workaround: Change VM timezones from US/Pacific-New to America/Los_Angeles, and then upgrade.

General Issues

  • Renaming the VMware Cloud on AWS cluster

    If a cluster is renamed in VMware Cloud on AWS, and as a result of renaming the cluster, if the management resource pool names change in VMware Cloud on AWS, then the following limitations are seen in vRealize Operations:

    • The view, "VMC Management Resource Pool" and the dashboard, "VMC Management VM Monitoring" excludes the management resource pool objects from the cluster that was renamed. As a workaround, update the filter definition for the view "VMC Management Resource Pool" to use a "contains" constraint instead of an "is" constraint for the name attribute that matches the value of "Mgmt-ResourcePool".

    • Jobs that are run through Automation Central will include the VMware Cloud on AWS management VMs instead of excluding them. Use caution with jobs as they may cause interruptions in the management VM functionality in VMware Cloud on AWS. 

  • Agent install fails with the error: Connect to salt master

    When you install an agent to monitor applications using Telegraf, the following error may occur: Connect to Salt Master. The error occurs because the end point VM is unable to connect with the salt master.

    Workaround: Verify the ownership of the folders in /ucp/salt/pki/master in cloud proxy. The ownership must be admin/admin. If the ownership is not admin, reset permissions/ownership.

    1. Run the /ucp/ucp-config-scripts/ucp-firstboot.sh script and verify the permissions of the folder.

    2. Reinstall the agent after successful execution of the script.

    Agent install should be successful.

  • JBoss server running in domain mode does not support LCM using custom Telegraf

    You cannot deploy jolokia.war across all the servers that run as a part of the JBoss domain mode and hence metrics cannot be collected.

    Workaround: Monitoring domain mode configuration in JBoss is supported in open source Telegraf. You can deploy jolokia.war across multiple servers.

  • The Add button in the Manage Telegraf Agents page remains activated after the creation of an application service

    While monitoring specific application services using Telegraf, the Add button in the Manage Telegraf Agents page is active after the creation of the second instance of the following application services: MSIIS, Active Directory, Sharepoint, MSExchange, and Network Time Protocol.

    Workaround: Delete the previous configurations of the specific application services and configure a new one.

  • Concurrent activation or deactivation of plugins during application monitoring using suite-api does not work

    During application monitoring using suite-api, when you activate or deactivate plugins concurrently, plugin activation or deactivation does not work. An exception is logged in the ucpapi.log file.

    Workaround: Provide a gap of one second between each thread during activation or deactivation of the plugins using suite-api.

  • When you get an application instance's configuration status using a Rest-API call, a wrong status is returned when the same configuration was installed or uninstalled previously

    If you installed or uninstalled an application instance and then uninstalled or installed it respectively, the API returns "SUBMITTING" when you try to get the application instance install or uninstall configuration status using "GET /api/applications/agents/services/{taskId}/status".

    Workaround: While getting the application instance configuration status using the "GET /api/applications/agents/services/{taskId}/status" API, ensure that you use the latest performed task ID. The result of calls with older IDs is undefined.

  • When you upgrade from vRealize Operations 8.1 to 8.10, the Cassandra application service is displayed as Java Application in the Services Discovered/Configured column of the Manage Telegraf Agents tab

    During application monitoring, after you upgrade from vRealize Operations 8.1 to 8.10, the Cassandra application service is displayed as Java Application in the Services Discovered/Configured column of the Manage Telegraf Agents tab. This happens if the Cassandra application service is configured for monitoring in vRealize Operations 8.1, using the vRealize Application Remote Collector generic Java plugin.

    Workaround: Deactivate the Java plugin before you upgrade the vRealize Application Remote Collector agent on the VM. After upgrading the vRealize Application Remote Collector agent, the Cassandra plugin will be discovered and can then be activated.

  • System language settings affects service discovery

    Service discovery might not work if the system language is different from English. For languages different from English, network connection state values might be different from constants defined in standard RFCs.

    Workaround: None

  • Reconfigure the Project Price widget if the vRealize Automation 8.x integration is deactivated and then reactivated

    There is data missing in the Project Price widget of the Cloud Automation Project Price Overview dashboard when you deactivate and then reactivate an existing vRealize Automation 8.x integration.

    Workaround: Reconfigure the Project Price widget by completing the following steps:

    1. After you deactivate and then reactivate the vRealize Automation 8.x integration, navigate to Dashboards > vRealize Automation 8.x > Cloud Automation Project Price Overview dashboard.

    2. Edit the Project Price widget.

    3. Navigate to the Input data section.

    4. Select the '+' (Add Object) button and select the CAS World object from vRealize Automation Adapter 8.x > CAS World.

    5. Click OK.

    6. Navigate to the Output data in the same widget configuration mode. Search for and select the CAS Project Price View object from the list.

    7. Save the widget.

  • While monitoring applications, you cannot activate a plugin with the same fields till the plugin configuration is deleted

    An error message is displayed in the user interface of vRealize Operations that states the following: 'Failed to update resource: Resource with same key already exists'.

    Workaround: Manually delete the existing plugin configuration and then continue with the activation of the plugin. If the problem persists, delete the corresponding resource from the inventory.

  • Alerts from the vSAN adapter that correspond to vSAN health check tests are not canceled if the test is removed from the vSAN Health Service.

    vRealize Operations cannot detect and cancel deleted alerts.

    Workaround: Manually cancel the alert from the user interface of vRealize Operations.

  • Despite deleting ucp-adapter instance certificates, users can run actions

    If users delete ucp-adapter instance certificates, they can still run actions such as, start and stop an agent, configure remote checks, and so on.

    Workaround: None

  • HTTP Post Adapter is deprecated in vRealize Operations 7.0 and above

    Re-activating the HTTP Post Adapter can open vRealize Operations to security flaws.

    Workaround: Complete the steps in KB 60328.

  • The compliance score for a user with limited object visibility is the same as for a user with complete object visibility

    The compliance score is calculated for objects that are not visible (not assigned) to the current user.

    Workaround: Complete the following steps:

    1. Create a custom group with objects visible (assigned) to the user.

    2. For that group, apply a policy in which the needed set of compliance alert definitions is activated.

      If that set is activated only in one active policy (the one that is applied to the custom group), the compliance benchmark based on those alert definitions will display the correct score.

User Interface Issues

  • After upgrading cloud proxy and vRealize Operations to 8.10, the VM name is not appended to the MSSQL instance

    After upgrading cloud proxy and vRealize Operations to 8.10, the VM name is not appended to the MSSQL instance for existing or newly activated plugins.

    Workaround: None

  • The Last Year option in the date picker is not intuitive

    The Last Year option in the date picker indicates that the time range starts from the end of the previous month and goes back a year. It does not indicate a time range that spans one year from the current date or the whole previous year.

    Workaround: None

  • A PDF report file might not include all data from a widget that has a scrollbar

    When you generate a report that contains a custom dashboard with a widget that has a scrollbar, the downloaded PDF file might not include all the data in the widget.

    Workaround: Increase the height of the widget in the dashboard to fit all the data.

check-circle-line exclamation-circle-line close-line
Scroll to top icon