Happy to announce that vRealize Operations Manager 6.0.1 is now available
VMware vRealize Operations Manager 6.0.1
What's New
vRealize Operations Manager 6.0.1 is an update to vRealize Operations Manager 6.0. This release includes bug fixes and the following enhancements.
- Improved Enterprise Readiness
- User interface improvements correct issues in the Views and Reports content for vSphere Hosts and Clusters and add a hierarchical view in the Topology widget.
- Licensing improvements provide the ability to use the REST API to add a license key.
- Alert Definition Updates
- Improved alert definitions for vSphere clusters, hosts, and virtual machines, to better detect CPU and memory problems.
- Improved alert definitions for hosts and virtual machines in the vSphere 5.5 Hardening Guide, to identify and report more non-compliance issues.
- Added alert definitions to detect duplicate object names in vCenter and vSphere Storage Management Service errors. To identify duplicate object names in the vCenter Server system, the name-based identification feature must be enabled for the vSphere adapter.
- Removed alert definition that was reporting false positives for packets dropped in a network port.
Fixed Issues
- Blank metrics and resource counts in multiple-node cluster
When one node failed to retrieve metrics and resource counts for any reason, other nodes of a multiple-node cluster might also show blank metrics and resource counts. This behavior appeared on the Cluster Management page of the administration interface. Now, a node cannot cause another node to show blanks. Any blanks indicate a direct issue with that node.
- The analytics services failed to start after upgrading
If the cluster failed to start after about 30 minutes, you had to review the analytics-{node-GUID}.log files for errors in the ActivityDataService. If you found errors, the activity persistence files were corrupted, and you had to delete them.
- Option to bring cluster online was enabled with an unresponsive node present
If a node in a cluster becomes unresponsive while the cluster is offline, you must not bring the cluster online. However, the button to bring the cluster online was enabled. The button to bring the cluster online is now disabled.
- Taking a node offline sometimes resulted in a timeout message
When you took a cluster node offline, the following message sometimes appeared:
Communication Error: Timeout reached while trying to communicate with the server. Try refreshing the UI manually.
- Migrated users could gain additional permissions
After migrating a 5.x deployment to this version of vRealize Operations Manager, migrated users were able to perform tasks, such as creating dashboards, for which they might not have had permission in version 5.x.
- Database became unresponsive when temporary log files filled the disk partition
When you monitored many active resources and had long data retention times, the vRealize Operations Manager database could stop responding because temporary database log files filled the disk partition that held the /storage/log directory. This issue occurred in vRealize Operations Manager vApp deployments.
- License key could be added to Unlicensed group
The product allowed you to associate a license key with the Unlicensed group, which was incorrect.
- When the Scoreboard widget is in interaction mode, the user does not see the expected information after the refresh interval
The problem occurs when you follow these steps: The Scoreboard widget shows information about the selected object, as expected. The Scoreboard widget shows information according to the first configuration after the Refresh interval, not as expected. There is no error message.
- And many more anonymous bugfixes and improvements!
