vCenter Operations Manager 5.8.1 is now available
That's a maintenance release, fixing a number of issues.
What's New
vCenter Operations Manager 5.8.1 is the latest release of VMware's integrated operations suite, converging performance, capacity, and configuration management. This new release introduces the following enhancements.
Improved Enterprise Readiness
VMware vCenter Operations Manager 5.8.1 is an update to vCenter Operations Manager 5.8. vCenter Operations Manager 5.8.1 includes bug fixes.
Apache Tomcat Server Upgrade
This release introduces support for Apache Tomcat Server version 2.9.4.
Improved SMARTS outbound plugin
This release includes improvements to the SMARTS outbound plugin.
Google Maps API Upgrade
This release includes an update to Google Maps JavaScript API version 3 from version 2.
-----
Resolved Issues
vCenter Operations Manager 5.8.1 inlcudes fixes for the following issues found in prior releases.
- After depolying and configuring vCenter Operations Manager 5.8, logging into the Admin portal fails. While log in to the the Admin portal fails, using the same credentials to log in to the vSphere UI and custom UI is successful.
- After upgrading from vCenter Operations 5.7.0 or above to version 5.8, the /opt/vmware/vpostgres/1.0 directory is removed. Since the path is still set to include /opt/vmware/vpostgres/1.0/bin, this breaks the resetadminpwd.sh script. It also complicates trying to use psql while troubleshooting database issues.
- After upgrading to vCenter Operations 5.7.2 to version 5.8, you cannot cancel alerts by any users (local or LDAP imported) for the previous version of the vApp.
- When trying to change the admin/root password in vCenter Operations Manager (vApp) 5.8, an "Invalid current password" error is generated, even though the correct current password was entered. This occured during the initial deployment (when the passwords are admin/vmware) and after the initial deployment.
- Manage Resource tags > Manage location in Environment Overview fails to save the marker location for the tag and the markers fail to load for the locations on the Geo Widget.
- After restarting the vcopswebenterprise service, any Health Status widgets will lose their "tags to filter" configuration information. All other configuration information is retained.
- After upgrading ESXi 5.1 hosts to ESXi 5.5 hosts, the hosts in maintenance mode are no longer visible in vCenter Operations Manager in the vSphere UI.
- Users moved to different OU containers in Active Directory are unable to log in to vCenter Operations due to caching issues.
- The vApp version of vCenter Operations Manager uses a suboptimal kernel IO scheduler
The kernel IO scheduler is set to CFQ by default. Changing the setting to NOOP improves the performance.
Workaround: After installing or upgrading vCenter Operations Manager, restart the vApp to activate the NOOP setting for the IO scheduler. - An unregistered vCenter Server appears in the vSphere Client UI as registered and collecting data
If you unregister a vCenter Server from vCenter Operations Manager using the vCenter Operations Manager Administration portal, it is removed from the list of registered servers, but continues to display in the vSphere Client as registered and collecting data.
Workaround: To remove the vCenter Server as registered in the vSphere Client, restart vcopsweb on the UI VM. To do this, restart the Apache Tomcat web server by entering the command as root: service vcopsweb restart - Top-N Analysis widget does not respond to resource tag changes
You cannot change the resource tag that you selected in the initial Top-N Analysis widget configuration. Although you can edit the widget configuration and select a different resource tag, the new configuration has no effect and the widget continues to show the previously selected resource tag.
Workaround: None.
-----
FULL release notes: VMware vCenter Operations Manager 5.8.1
