Today marks the release of the next minor revision of vRealize Operation Manager (vROps) to 6.0.2.
Release Notes - https://www.vmware.com/support/vrops/doc/vrops-602-release-notes.html
This release fixes some cosmetic issues with the reports and fixes some of the analytics portion of the program. Here is the highlight.
Release Notes - https://www.vmware.com/support/vrops/doc/vrops-602-release-notes.html
This release fixes some cosmetic issues with the reports and fixes some of the analytics portion of the program. Here is the highlight.
This section contains issues that have been resolved in this release.
- Time Remaining badge on the Analysis tab shows "?"
After policies are edited multiple times, the breakdown on the Time Remaining badge displays "?".
This issue is resolved in this release. - Verisign certificates are not migrated during an upgrade
After updating the trustore file with Verisign certificates for vRealize Operations Manager 6.0 and upgrading to 6.0.1, the certificates are not available. Updating the trustore file is a customization step required to support the AWS adapter.
This issue is resolved in this release. - vCenter Operations Manager 5.8.x custom dashboards migrated to vRealize Operation Manager 6.0 show no data or display incorrectly
When you migrate vCenter Operations Manager 5.8.x custom dashboards to vRealize Operation Manager 6.0, the dashboards do not show any data or might not show resource names as expected.
This issue is resolved in this release. - After applying the hot fix for vRealize Operations Manager 6.0.1, the VIN adapter still does not collect data properly
After applying the hot fix documented in KB 2110330, the VIN adapter still does not collect data properly. Data appears as question marks in the UI.
This issue is resolved in this release. - vRealize Operations Manager sizing guidelines for high availability
Enabling High Availability (HA) in the sizing guidelines sheet for vRealize Operations Manager doubles the system load and through-put requirements. In earlier releases, the sizing guidelines sheet rounded-up the nodes to the next whole number before they were doubled. This issue is resolved in this release. Effective in this release, the sizing guidelines sheet doubles the nodes before they are rounded-up to the next whole number.
This issue is resolved in this release.
Comments