vCenter Server 6.0.0b Release Notes

|

Updated on: 07 July 2015

vCenter Server 6.0.0b | 07 JULY 2015 | ISO Build 2800571

vCenter Server Appliance 6.0.0b | 07 JULY 2015 | ISO Build 2800571

vCenter Server 6.0.0b on Windows | 07 JULY 2015 | Build 2776511

vCenter Server 6.0.0b on vCenter Server Appliance | 07 JULY 2015 | Build 2776510

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

This release of vCenter Server 6.0.0b delivers a number of bug fixes that have been documented in the Resolved Issues section.

Earlier Releases of vCenter Server 6.0

Features and known issues of vCenter Server are described in the release notes for each release. Release notes for earlier releases of vCenter Server 6.0 are:

VMware vCenter Server 6.0.0a Release Notes
VMware vSphere 6.0 Release Notes

For compatibility, installation and upgrades, product support notices, and features see the earlier release notes of vCenter Server

VMware vSphere 6.0 Release Notes

Patches Contained in this Release

This release of vCenter Server 6.0.0b delivers the following patches. See the VMware Patch Download Center for more information on downloading patches.

Internationalization

VMware vSphere 6.0 is available in the following languages:

  • English
  • French
  • German
  • Japanese
  • Korean
  • Simplified Chinese
  • Traditional Chinese

Components of VMware vSphere 6.0, including vCenter Server, ESXi, the vSphere Web Client, and the vSphere Client do not accept non-ASCII input.

Resolved Issues

vCenter Single Sign-On Issues

  • vCenter Server fails to display the node count within the environment for a user
    Users from domains other than the system tenant's system domain are not considered a Configuration User and cannot utilize the privileges afforded by the SystemConfiguration.Administrators group. On the System Configuration page, you might not be able to see any of the nodes present or any of the services on an embedded vCenter Server Windows.

    This issue is resolved in this release.

Upgrade and Installation Issues

  • VPXD SSL certificates might not be migrated after upgrade to vCenter Server 6.0
    After you upgrade from vCenter Server 5.5 to 6.0 using an external Single Sign-On, the VPXD SSL certificates might not be migrated if the VPXD certificate is replaced by custom certificate prior to upgrade.

    This issue is resolved with this release.

Security Issues

  • The Network Time Protocol (NTP) package is updated
    The NTP package is updated to address a stability issue.

Storage Issues

  • vApp creation fails when storage DRS is enabled
    When you use vCloud Director 5.5.3 with vSphere 6.0, any operation that clone a vApp, including add to my cloud, instantiate a vApp template, copy, relocate, or import a vApp might fail when the target virtual data center includes a storage DRS-enabled storage cluster that does not support source virtual machine's storage profile.

    This failure logs an error message similar to the following:

    Could not find datastore to create VM ...
    Cannot use datastore [vcId=nnnn, moref=datastore-nn] since it does not support storage policy SDRS_SP

    This issue is resolved in this release.

  • Attempts to register a VASA provider fails with an error
    Attempts to register a VASA Provider in the vCenter Server might fail with an error similar to the following:

    A problem was encountered while registering the provider

    This is issue is resolved in this release.

Server Configuration Issues

  • Event information is duplicated in the snmp trap message
    The event information is duplicated in the snmp trap message. Messages such as NetworkRedundancyLostAlarm has duplicated messages in String= field.

    This issue is resolved in this release.

vCenter Server, vSphere Client, and vSphere Web Client Issues

  • All Users Tasks is no longer disabled by default in the vSphere Web Client
    In the Recent Tasks view of vSphere Web Client, My Tasks is displayed to the user on first time login. It enables the user to switch to All Users Tasks to see other users' tasks when the global flag show.allusers.tasks is set to true in webclient.properties file.

    In addition, the preferred selection between My Tasks and All Users Tasks is retained across all sessions and is displayed to the user when the user logs in to a new session.

    Note: To optimize performance in case of large vSphere inventories disable All Users Tasks

  • Attempt to delete vSphere Distributed Switches fail
    Attempting to delete vSphere Distributed Switches (VDS) fail when VPX_DVPORT_MEMBERSHIP and VPX_DVPORT tables have conflicting port entries and the proxy host of the port does not exist in the inventory of vCenter Server.

    This issue is resolved in this release.

  • Host Profile compliance check for clusters fails with error when the vCenter Server is installed in a non-default directory
    Host Profiles compliance check for a cluster fails with the error:
    A general system error occurred: Runtime fault

    During installation of vCenter Server, ProgramData is installed on a different system drive instead of Program Files

    In the ProgramData/VMware/vCenterServer/logs/vmware-vpx/vpxd.log file, you see errors similar to the following:

    <YYYY-MM-DD>T<TIME> info vpxd[06552] [Originator@6876 sub=Default opID=C16BF883-00000114-7] [VpxLRO] -- ERROR task-4684 -- MoComplianceManager -- vim.profile.ComplianceManager.checkCompliance:

    vmodl.fault.SystemError:
    --> Result:
    --> (vmodl.fault.SystemError) {
    --> faultCause = (vmodl.MethodFault) null,
    --> reason = "Runtime fault",
    --> msg = "Received SOAP response fault from [local]: checkClusterCompliance
    --> Required field "message" not provided (not @optional)"
    --> }
    --> Args:
    -->
    --> Arg profile:
    --> (ManagedObjectReference) [
    --> 'vim.profile.cluster.ClusterProfile:5CB595B6-421A-42F4-9A45-A64F35EE8CAB:clusterprofile-1',
    --> 'vim.profile.host.HostProfile:5CB595B6-421A-42F4-9A45-A64F35EE8CAB:hostprofile-301'
    --> ]
    --> Arg entity:
    --> (ManagedObjectReference) [
    --> 'vim.ClusterComputeResource:5CB595B6-421A-42F4-9A45-A64F35EE8CAB:domain-c119'
    --> ]

    This is issue is resolved in this release.

  • vCenter Server service fails to start on reboot after you apply access control lists
    vpxd fails to start on reboot after you apply access control lists or traffic filtering rules to the vSphere Distributed Switches (VDS) port group.

    This issue is resolved in this release.

  • vSphere Web Client displays vApp and VM templates as Unknown when you delete their content in a subscribed library
    If you are using subscribed library with enabled option to download library content only when needed, when you delete the content of a VM template, the vSphere Web Client displays the VM template as Unknown, and the item becomes unusable. Same behavior occurs for vApp templates in the subscribed library.

    This issue is resolved in this release.

  • Internal Server Error occurs if Tagging Description Field is Empty
    The Tag Category Description field is optional in the vSphere Web Services API, but it is mandatory in the vCloud Suite SDK. Therefore, if the description field is empty, the vCloud Suite SDK can return an internal server error that states, "the ‘description’ field of the Category model is empty".

    This is issue is resolved in this release.

  • SNMP alerts display IP as 0.0.0.0 instead of the vCenter Server IP address after upgrading to vCenter Server 6.0
    When you use SNMP receiver to receive SNMP trap messages, the information from vCenter Server appears to originate from an incorrect IP address 0.0.0.0. This issue occurs after upgrading the vCenter Server to version 6.0.

    This issue is resolved in this release.

  • Inventory Service fails to start following a vCenter Server reboot
    Inventory Service fails to start after restarting the vCenter Server. An error similar to the following is displayed:

    "The VMware Inventory Service service terminated with service-specific error Incorrect function.."

    This is issue is resolved in this release.

  • vCenter Server for Windows and vCenter Server Appliance installations fail when you use an external database with manually customized database objects
    While using an external database with manually created database objects, the installation fails. The installer displays error messages similar to the following:

    install.vdcs.db.version.check.error and Installation of component VCSService Manager Failed with error code 1603.

    This issue is resolved by creating additional database objects during installation.

    This issue is resolved in this release.

Virtual Machine Management Issues

Content Libraries Issues

  • Libraries backed by NFS are unable to access storage after the vCenter Server Appliance is rebooted
    Libraries backed by NFS are unable to access storage after a successful reboot of vCenter Server Appliance. This results in loss of access to data stored in the library content of NFS server, making it inaccessible to the users.

    This issue is resolved in this release.

Known Issues

For other existing issues that have not been resolved and documented in the Resolved Issues section, please see Known Issues section in the VMware vSphere 6.0 Release Notes.