VMware vRealize Operations Manager 8.0.1 | 2019 | Build 15331180
VMware vRealize Operations Manager Upgrade Pack from 6.6.1, 6.7, and 7.x to 8.0.1 | 2019 | Build 15331198
Note: This upgrade .pak file includes the OS upgrade files from SUSE to Photon and the vApp upgrade files
VMware vRealize Operations Manager Upgrade Pack from 8.x to 8.0.1 | 2019 | Build 15331178
Note: This upgrade .pak file includes the vApp upgrade files for the Photon OS based vApp. There is no Photon to Photon OS .pak file released for 8.0.1.
VMware vRealize Operations Manager 8.0 Endpoint Operations Agents | 2019 | Build 14827011
VMware vRealize Operations Manager 8.0 Endpoint Operations Agents PAK Updates | 2019 | Build 14827024
VMware vRealize Operations Manager 8.0.1 Pre-Upgrade Assessment Tool | 2019 | Build 15282762
VMware vRealize Application Remote Collector 8.0.1 | 2019 | Build 15214071
Check frequently for additions and updates to these release notes.
What's in the Release Notes
The release notes cover the following topics:
- What's New?
- System Requirements
- Installing and Updating vRealize Operations Manager
- Resolved Issues
- Known Issues
This is a maintenance release of vRealize Operations Manager in which issues related to performance and stability have been fixed. In addition, corner case issues that customers might encounter in their environments during upgrade of the product have also been fixed. For the list of fixed issues, please refer to the Resolved Issues section.
Review this section before you install or update vRealize Operations Manager.
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.
You can deploy vRealize Operations Manager 8.0.1 with VMware virtual appliance.
If you are deploying a vRealize Operations Manager virtual appliance, 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 Manager virtual appliance must be deployed on hosts that are:
- ESX/ESXi 6.0 or later (with the exception of ESX/ESXi 6.5 that must be with a patch not lower than ESX/ESXi 6.5 Update 1) and managed by VMware vCenter Server 6.0 or later.
- ESX/ESXi 6.5 with build number lower than 5969303 must be updated to a higher patch.
- If you have vRealize Operations Manager virtual appliance deployed on ESXi 5.5 hosts, you must first upgrade the vCenter Server to versions 6.0 or 6.5, and then upgrade to vRealize Operations Manager 8.0.1.
Applying License Keys
IMPORTANT: A new license key is required for upgrading vRealize Operations Manager 7.0 and later versions. All license keys except vRealize Operations for Horizon, vSOM Enterprise Plus and its add-ons are invalidated. The product will work in evaluation mode until a new valid license key, which can be obtained from the MyVMware portal, is installed. After you log in to the user interface of vRealize Operations Manager, if you see that you are using an evaluation license, consider applying for a new license before the end of the 60-day evaluation period.
For more details on entitlements of vRealize Operations editions, see the edition comparison table from the following link: https://www.vmware.com/products/vrealize-operations.html.
To ensure compliance of your vSphere, VMware Cloud on AWS, and vSAN 6.7, 6.5, and 6.0 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 Manager 8.0.1 includes compliance alerts for VMware vSphere Security Configuration Guide versions 6.7 Update 1, 6.5, and 6.0. 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.
In addition to the VMware solutions (vSphere, Endpoint Operations Management, and vRealize Log Insight), see the Solution Exchange marketplace for many more solutions. These solutions work with Virtual Appliance single or multiple nodes.
When you upgrade your vRealize Operations Manager instance to 8.0.1, both TLS 1.0 and TLS 1.1 are disabled on all the vRealize Operations Manager nodes. TLS 1.2 is the only protocol that will be supported by default. However, if you want to lower the security bar and enable TLS 1.0 and 1.1, you can still do so, see KB 74951 for more information. TLS 1.0 and TLS 1.1 settings are preserved during upgrade.
VMware Product Compatibility
Note: The VMware Product Interoperability Matrix provides details about the compatibility of vRealize Operations Manager with VMware products.
This vRealize Operations Manager release supports all current Web browsers, although only the following browsers were tested with this release:
- Google Chrome: Version 76 and 77
- Mozilla Firefox: Version 68 and 69
- Microsoft Internet Explorer: Version 11 (limited support)
- Microsoft Edge 17 and 18
- Safari 12 and 13
Note: There are two different upgrade .pak files to upgrade to vRealize Operations Manager 8.0.1:
- To upgrade from vRealize Operations Manager 6.6.1, 6.7, 7.0, or 7.5 to vRealize Operations Manager 8.0.1 you must download and apply the vRealize Operations Manager 6.6.1, 6.7, 7.0, and 7.5 Virtual Appliance upgrade .pak file.
- To upgrade from vRealize Operations Manager 8.0 to 8.0.1 you must download and apply the vRealize Operations Manager 8.0 Virtual Appliance upgrade .pak file.
Note: While upgrading to vRealize Operations Manager 8.0.1, the expected size of the root partition for Photon OS is 20 GB. For information about this requirement, see KB 75298.
It is always recommended to run the Pre-Upgrade Assessment tool before an upgrade. This tool provides you with an impact analysis following the reduction of metrics in various versions of the product as well as with the validation check results of the systems upgrade ability. A pre-upgrade assessment report that is generated provides you with recommended metric replacements and as well as with recommendations if the system does not pass the validity checks. For more details on using the Pre-Upgrade Assessment Tool, see KB 74952.
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 Manager.
Refer to the vRealize Operations Manager vApp Deployment and Configuration Guide that provides guidance for a vRealize Operations Manager virtual appliance, before you install or update vRealize Operations Manager.
Upgrading to vRealize Operations Manager 8.0.1, resets out-of-the-box content as part of the software upgrade process even if the Reset Default Content button is unchecked during the upgrade. 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 Manager 8.0.1.
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 Manager by using vRealize Suite Lifecycle Manager. For more information, see Creating an Environment. To automate installation, configuration, upgrade, patch, configuration management, drift remediation and health from within a single pane of glass, you can use vRealize Suite Lifecycle Manager. If you are a new user, click here to install vRealize Suite Lifecycle Manager. This provides IT managers or cloud admin resources to focus on business-critical initiatives, while improving time to value (TTV), reliability, and consistency.
See the Installation and Upgrade Issues section for issues related to installing vRealize Operations Manager or updating the software.
The rsyslog service does not run with vRealize Operations Manager parameters.
After Service Discovery is configured, the Execute Script and Get Top Processes actions do not work from the Inventory > Objects page.
The Set Memory of VM action does not work and the memory hot plug is not supported on virtual machines.
CPU usage on a vRealize Operations Manager node is at 100% because of complex relationship updates.
Collectors stop when the thread count exceeds the limit.
Only one snapshot is displayed in a VM even though more than one snapshot is created.
An error occurs when you try to publish a dashboard with the Session Processes widget.
When you upgrade from vRealize Operations Manager 7.5 to 8.0, configurations and vCenter Server users are lost.
vCenter Server users cannot log in to vRealize Operations Manager 7.5.
Logging for Apache services are not configured properly under the Photon operating system. There are missing log rotation configurations for several services.
The known issues are grouped as follows.Installation and Upgrade Issues
- Batch installation ignores the custom certificate
During a multi-node cluster deployment, the deployment wizard ignores the custom certificate even if it is provided and uses the default certificate.
- The Take Node(s) Offline wizard appears when you try to bring an offline RC node online
When you try to bring an RC node back online after having just taken it offline, the Take Node(s) Offline wizard appears when you click the Take Node Offline/Online button, instead of the Take Node(s) Online wizard as expected.
Workaround: If the node state still displays as Running or the status is still Online after having taken it offline, wait a few moments and then manually refresh the data in the view from the top menu to get the latest state of the node. After the correct state is displayed which is Not Running, the Take Node Offline/Online button will work as expected.
- Node replacement fails while replacing all nodes in the fault domain
If the nodes that are replaced are not powered off, it might result in an unusable state of the cluster.
Workaround: While replacing nodes in a CA enabled cluster, ensure that the nodes are powered off.
- Nodes are marked as Configured instead of New
When the Multiple Nodes Addition wizard detects that a wrong admin password is provided, node addition is canceled, but new nodes are marked as Configured.
Workaround: Redeploy the nodes and restart with a correct admin password.
- Even if the cluster state is set to Failure, the cluster is functional
The state of the cluster is incorrectly set to Failure if you use the Bring Online button from the witness node.
Workaround: Do not use the witness node to bring the cluster online.
- Installation of a management pack fails on a newly added node
After you upgrade to vRealize Operations Manager 8.0.1, installation of a management pack fails on a newly added node.
Workaround: Upgrade management packs to their latest version and then add a new node.
- Upgrade to vRealize Operations Manager 8.0.1 fails for instances with Wavefront configuration
If you use vRealize Operations Manager 7.5 and earlier versions with Wavefront configured, you cannot upgrade to vRealize Operations Manager 8.0.1 as upgrade fails.
- In a pure IPv6 environment, DNS servers are missing from the /etc/resolv.conf file
DNS servers are missing from the /etc/resolv.conf file when a new node is deployed in a pure IPv6 environment. As a result, the node cannot resolve FQDNs to IP addresses.
Workaround: With the help of your network administrator, manually set the DNS servers in the /etc/resolv.conf file.
- 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 Manager 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.
- 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 Manager 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.
- 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:
- Create a custom group with objects visible (assigned) to the user.
- For that group, apply a policy in which the needed set of compliance alert definitions is enabled.
If that set is enabled 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.
- Historical data is not displayed for application plugins if the vCenter PNID is modified
The historical data or data prior to changing the vCenter PNID is lost for the application plugins.
- SharePoint service is not discovered with Service Discovery
Since IIS and SharePoint services have common ports, IIS takes the ports from SharePoint and the SharePoint service is not discovered with service discovery.
- The status of a few plugins is Unknown after vRealize Application Remote Collector and vRealize Operations Manager is upgraded from 7.5 to 8.0.1
When you upgrade vRealize Application Remote Collector and vRealize Operations Manager from 7.5 to 8.0.1, the Unknown icon is displayed along with a gray icon.
Workaround: Reactivate the plugin.
- Upgrade from vRealize Operations Manager 7.5 to 8.0.1 results in a change in the license cost driver
When you upgrade from vRealize Operations Manager 7.5 to 8.0.1, there is a change in the license cost driver between the Summary page and the License Cost Driver page.
Workaround: You can set the cost with the old value, which is $365, in the License Cost Driver page.
- vRealize Automation 8.x stops collecting data
- If vRealize Automation 8.x services have stopped, data is not collected.
- When vRealize Automation 8.x services are running, data is not collected intermittently.
- Start vRealize Automation 8.x services and ensure that all the vRealize Automation 8.x services are running. Wait for about 20 mins.
- Restart the vRealize Automation 8.x adapter instance.
- While installing an application monitoring agent using an Internet Explorer browser, a message is displayed asking the user to save or open a json file locally
When you install an application monitoring agent and upload a credentials csv file using Internet Explorer, the browser displays a message asking you to save or open a json file locally. You will not be able to proceed to the next screen.
Workaround: Use a different browser.
- Additional cost displayed is zero even though there is a direct cost associated with the VM
If the vCenter Server configured with vRealize Automation 8.x was already monitored by vRealize Operations Manager and costs were computed, the cost is displayed as zero.
Workaround: Cost will match the price from the next month when both get a fresh month-to-date start.
- Collection for the Management Pack for Microsoft Azure fails when the network connection times out
When the Management Pack for Microsoft Azure sends a request to the Azure portal and the portal takes a longer time to read the request than the Azure SDK timeout value, collection for the adapter instance fails. Collection resumes when the network timeout issue is resolved or the Azure portal can read the request.
- Change in the way Active Directory authentication source handles user names
Logging in to vRealize Operations Manager 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.
Workaround: To authenticate using short name, configure the Active Directory authentication source to use
samAccountName for Common Name. You must re-import the Active Directory users and groups after setting the Common Name to samAccountName.
- Objects such as images and icons related to the Management Pack for SDDC Health, Management Pack for OpenStack, and Management Pack for SRM are not displayed
After you upgrade vRealize Operations Manager, if you scale a vRealize Operations Manager cluster with the Management Pack for OpenStack 5.0, or Management Pack for SRM 8.1, or Management Pack for SDDC Health 5.0 installed and add another vRealize Operations node, some objects such as images and icons related to the management packs are missing.
Workaround: Users with an instance of the Management Pack for OpenStack, or Management Pack for SRM, or Management Pack for SDDC Health must uninstall the management packs, before upgrading vRealize Operations Manager.
- Cost computation is not supported for a VMware Cloud vCenter Server end point in vRealize Operations Manager 8.0.1
In vRealize Operations Manager 8.0.1, when you add a VMware Cloud vCenter Server end point and specify the cloud type as VMware Cloud on AWS, cost is not computed for the VMware Cloud vCenter Server end point, because the cost model is different from on-premises vCenter Servers.
Workaround: The cost of infrastructure coming from VMware Cloud on AWS can be managed using the vRealize Operations Manager management
pack for VMware Cloud on AWS.
- Interactions in a distribution type of view, work only for the Current type of transformation
When you create a distribution type of view and select a transformation type that is not Current, the list view is not displayed.
Workaround: Change the selected metric transformation to Current to see the list view. You can add the same metric as an additional
column with a relevant transformation (for example, maximum) and view the result of the transformation in the list view.
- 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 Manager cannot detect and cancel deleted alerts.
Workaround: Manually cancel the alert from the user interface of vRealize Operations Manager.
- When using Internet Explorer 11 to access the Log Insight tab pages and dashboards, the data is blocked
When using Internet Explorer 11 to access the Log Insight tab pages and dashboards, data is blocked, and the page remains blank.
Workaround: Use the Firefox or Chrome browser.
- Generated reports may be blank
If you log in to vRealize Operations Manager with vCenter Server credentials and generate a report, the generated report is always blank.
- The dashboard link cannot be opened when you use Internet Explorer on Windows 7
When you try to open a dashboard that is a shared URL, the page does not open.
Workaround: You must not use Internet Explorer with Windows 7. Open the link using other browsers.
- 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.
- The filter menus in the Policies workspace step called Collect Metrics and Properties, do not work correctly
When you deselect an option from the State, KPI, or DT drop-down menus, the filter hides all attributes irrespective of their settings.
Workaround: Save and reopen the policy.
- 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.