vcenter patches

do anyt of the updates applied to vcenter address security bugs (and I am on about the vcenter application not the underlying OS), or are they more geared towards functionality bugs. Is there anywhere you can see what kinds of issues each update covered?
LVL 3
pma111Asked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
vCenter Server Updates do fix security bugs, as well as functionality issues and bugs which have been found.

see here, the OpenSSL, HeartBleed issues, was found in vCenter Server

a security fix was made available to fix this security flaw.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2076692

The release notes always detailed the fixes, and Resolved issues see here

https://www.vmware.com/support/vsphere5/doc/vsphere-vcenter-server-55u2d-release-notes.html

These are the resolved issues for vCenter Server 5.5 Update 2d

(the release notes also detail current known issues with the Update)

Resolved Issues

The resolved issues are grouped as follows:

vCenter Single Sign-On
Networking
vCenter Server, vSphere Client and vSphere Web Client
Virtual Machine Management
vMotion and Storage vMotion
vCenter Single Sign-On

 VMware Directory Service consumes excessive memory
In an vCenter Single Sign-On multi site replication environment, the VMware Directory Service (vmdird.exe) might consume a large part of the available RAM, respond slowly, or might stop responding when it fails to make the Kerberos bind.

This issue is resolved in this release.

 Backup and restore of vCenter Single Sign-On database might not replicate the data between primary and secondary nodes correctly
When you backup and restore the vCenter Single Sign-On database on multiple nodes, after a successful restore, the data might not be identically replicated between the primary and the secondary nodes.

This issue is resolved in this release.

 Attempts to logout through the vCloud Automation Center UI might fail
When you attempt to logout through the vCloud Automation Center (vCAC) UI, the logout attempt fails and you are re-logged in without any authentication instead of being redirected to the vCAC login page.

This issue is resolved in this release.
Networking

 Network Interface Cards of virtual machines in disconnected state might get ejected during vMotion
When you perform a vMotion and connect with virtual machines that have their Network Interface Cards (NICs) in an disconnected state, that is the Connected checkbox in the virtual machine's Edit Settings tab is unchecked, the NICs of such virtual machines might display an error similar to the following and get ejected:

Invalid Configuration Device 0

This issue is resolved in this release.
vCenter Server, vSphere Client, and vSphere Web Access

 Virtual machines on ESXi hosts containing NSX Endpoint virtual machines might not power on
When virtual machines with NSX Endpoint installed are deployed on an ESXi host, the virtual machines residing on such an ESXi host might not Power On after a vCenter Server restart.

This issue is resolved in this release.

 Update to SUSE Linux Enterprise Edition Server in vCenter Server Appliance to address time zone changes
Russia has subtracted an hour from most of its time zones on 26 Oct 2014 at 02:00 local time. With this change Russia updated its seven existing time zones, with the addition of three new time zones and the merging of four time zones. SUSE Linux Enterprise Edition Server in vCenter Server Appliance is updated to address the changes in the Russian time zone. For more information on time zones, see KB 2092554.

 vpxd reports massive logging
The performance of the vCenter Server is affected due to massive logging of vpxd logs. The vpxd.log file reports several entries similar to:
[06472 error 'vpxdvpxdMoHost'] [MoDVSwitch::HandleAsyncQueryPerfResults]InstanceId: host-516 2458
[05968 error 'vpxdvpxdMoHost'] [MoDVSwitch::HandleAsyncQueryPerfResults]InstanceId: host-2378 3068
[06520 error 'vpxdvpxdMoHost'] [MoDVSwitch::HandleAsyncQueryPerfResults]InstanceId: host-2318 2349
[06108 error 'vpxdvpxdMoHost'] [MoDVSwitch::HandleAsyncQueryPerfResults]InstanceId: host-504 2219
[02260 error 'vpxdvpxdMoHost'] [MoDVSwitch::HandleAsyncQueryPerfResults]InstanceId: host-531 3144

This issue is resolved in this release.

 Accessing the Storage View tab fails with the error
The Storage Monitoring Service fails to initialize and displays an error while accessing the Storage View tab in vCenter Server.

Request failed. Server took to long to respond

The sms.log file at C:\ProgramData\VMware\VMware VirtualCenter\Logs contains an entry similar to the following:

ERROR com.vmware.vim.sms.provider.vc.PopulateMultipathingEntityTask -
PopulateMultipathingEntityTask Failed for entity : datastore
entityRelType : cluster :
java.lang.NullPointerException
        at com.vmware.vim.sms.provider.vc.PopulateMultipathingEntityTask.
populateEntityMultipathingStatus(PopulateMultipathingEntityTask.java:166)
        at com.vmware.vim.sms.provider.vc.PopulateMultipathingEntityTask.run
(PopulateMultipathingEntityTask.java:43)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

The ds.log file at C:\ProgramData\VMware\Infrastructure\Inventory Service\logs contains an entry similar to the following:

ERROR com.vmware.vim.query.server.query.impl.ServiceImpl] Error running
query:com.xhive.error.XhiveInterruptedException: INTERRUPTED
 at xDB_9_0_11.iD.nA(xdb:166)
 at xDB_9_0_11.iD.nC(xdb:176)
 at xDB_9_0_11.Kx.nC(xdb:218)
 at xDB_9_0_11.Hv.EW(xdb:1798)
 at xDB_9_0_11.Hv.As(xdb:1892)
 at xDB_9_0_11.ds.j(xdb:81)
 at xDB_9_0_11.lP.e(xdb:32)
 at xDB_9_0_11.lP.ry(xdb:93)
 at xDB_9_0_11.lP.rB(xdb:146)
 at xDB_9_0_11.lP.rD(xdb:163)
 at xDB_9_0_11.lP.rF(xdb:184)
 at xDB_9_0_11.Hd.aV(xdb:50)
 at xDB_9_0_11.ls.aU(xdb:112)
 at xDB_9_0_11.CP.aV(xdb:52)

This issue is resolved in this release.

 Scheduled tasks cannot be created for a different time on the same day in vSphere Web Client
Scheduling tasks for a different time on the same day fails in vSphere Web Client on a system that does not have a string value configured for AM and PM in the time settings.

This issue is resolved in this release.

 The VMware VirtualCenter Server service fails intermittently
The VMware VirtualCenter Server service (vpxd.exe) might fail intermittently due to an error in the vpxd-snmp code path. This issue is resolved in this release.
 HTML console cannot be launched with custom port
Attempting to use vSphere webclient to launch HTML V5 console after upgrading the vCenter Server appliance from 5.5 U1 to 5.5 U2b fails with an error similar to the following:

Secure Connection Failed

An error occurred during a connection to 10.5.99.3:8559. SSL received a record that exceeded the maximum permissible length. (Error code: ssl_error_rx_record_too_long)

The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the web site owners to inform them of this problem.

This issue is resolved in this release. For more information see KB 2103331.

 Datastore browser in vSphere Web Client does not overwrite existing files.
When a new file with an existing file name is uploaded to a folder in datastore, the new file does not replace the existing file. The old file is retained although the upload task is marked as successfully completed.

This issue is resolved in this release.

 VMware VirtualCenter Server service fails
The VMware VirtualCenter Server service fails with foreign key constraint violation. This error might occur while removing the cluster with Virtual Storage Area Network (VSAN) and High Availability (HA) with Distributed Resource Scheduler (DRS) enabled and containing hosts which are fail over hosts or hosts with dpm configuration enabled. In the vpxd log of vCenter Server, you see entries similar to:

[12232 warning 'Default' opID=SWI-7dd30db3] [VdbStatement] SQL execution failed: INSERT INTO VPX_COMPUTE_RESOURCE_VSAN_HOST WITH (ROWLOCK) (COMP_RES_ID, HOST_ID, NODE_UUID, CLUSTER_UUID, AUTOCLAIM_STORAGE, ENABLED) VALUES (?, ?, ?, ?, ?, ?)
[12232 warning 'Default' opID=SWI-7dd30db3] [VdbStatement] Diagnostic data from driver is 23000:1:547:[Microsoft][SQL Server Native Client 11.0][SQL Server]The INSERT statement conflicted with the FOREIGN KEY constraint "FK_COMP_RES_VSAN_REF_HOST". The conflict occurred in database "vCenter", table "dbo.VPX_HOST", column 'ID'.
[12232 error 'Default' opID=SWI-7dd30db3] [VdbStatement] SQLError was thrown: "ODBC error: (23000) - [Microsoft][SQL Server Native Client 11.0][SQL Server]The INSERT statement conflicted with the FOREIGN KEY constraint "FK_COMP_RES_VSAN_REF_HOST". The conflict occurred in database "vCenter", table "dbo.VPX_HOST", column 'ID'." is returned when executing SQL statement "INSERT INTO VPX_COMPUTE_RESOURCE_VSAN_HOST WITH (ROWLOCK) (COMP_RES_ID, HOST_ID, NODE_UUID, CLUSTER_UUID, AUTOCLAIM_STORAGE, ENABLED) VALUES (?, ?, ?, ?, ?, ?)"

This issue is resolved in this release.

Virtual Machine Management

 Cloning or deploying deploying virtual machines over the network causes performance degradation.
When deploying virtual machines from a shared storage location to ESXi hosts with non-shared storage as the destination, the deployment occurs across the network using NFC. This causes the source ESXi host to perform a file copy across the network, as opposed to using local copy methods on the destination ESXi Host, causing possible performance degradation.
This issue is resolved in this release.

 Alert event is not triggered when one VM has multiple vNICs with same MAC address
Neither VmStaticMacConflictEvent nor VmMacConflictEvent alerts are triggered when a VM has multiple Virtual Network Interface Cards (vNIC) configured with same MAC address. This results in not triggering the alarms for the scenario of duplicate mac addresses within same VM, which leads to conflicts while deleting the VM.

This issue is resolved in this release.

vMotion and Storage vMotion

 The default behavior of DRS has been changed to make the feature less aggressive during cluster upgrade
The default upper limit of Distributed Resource Management (DRS) while putting hosts on maintenance mode during a cluster upgrade is 150%. This issue is resolved by adding a configuration property. For more information see KB 2104983.

Source
https://www.vmware.com/support/vsphere5/doc/vsphere-vcenter-server-55u2d-release-notes.html
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.