VMware has become aware of an issue that occurs after 90 days after deployment of a template in vCloud Automation Center (vCAC) 6.0.x, tenants become inaccessible and identity stores disappear due to expiration of the tenant admin password. For more information, see the article below.
For further information and updates, please refer to KB article: vCloud Automation Center 6.0.x tenants become inaccessible and identity stores disappear (2075011) in your problem description.
Note: Any updates to this issue will be reflected in the aforementioned KB article. To be alerted when this article is updated, click Subscribe to Document in the Actions box on the KB article page.
This week, a new vulnerability was discovered affecting SSL, a protocol most of the Internet uses to encrypt and secure communications. The VMware Security Engineering, Communications, and Response group (vSECR) is investigating the OpenSSL issue dubbed “Heartbleed”. For information on which VMware products may be affected and resolution/remediation steps, refer to the two KB articles at the bottom of this post.
For the curious, we would like to quickly explain why this particular vulnerability could be a risk across the Internet. The bug — dubbed “Heartbleed” — allows anybody to read the memory on a system that is supposed to be protected by SSL.
An anonymous attacker could potentially steal any information from an SSL-secured communication when the issue is not addressed. Best practices dictate that websites and web service providers should always use SSL-encrypted communication when dealing with sensitive information like usernames, passwords, and bank info. Heartbleed could breach that information to anybody who knows how to extract it without leaving a trace.
VMware has become aware of an issue that occurs after upgrading to vCloud Networking and Security (vCNS) 5.1.3 in an environment with Cisco Nexus 1000V. The vShield Manager user interface becomes unavailable.
A hot patch fix is available. This does not affect customers with VMware standard or VMware vDS switches.
If you encounter this issue, file a support request with VMware Technical Support and note Knowledge Base article: vShield Manager user interface becomes unavailable after upgrading to 5.1.3 when Cisco Nexus 1000V is present (2073502) in your problem description.
Note: Updates on this issue will be reflected in the aforementioned KB article. To be alerted when this article is updated, click Subscribe to Document in the Actions box on the KB article page.
VMware has become aware of an issue wherein after upgrading to vCloud Connector 2.6, a change to the permissions on the staging directory causes transfers to fail.
A newly installed vCloud Connector node has read/write/execute permissions for user, group, and other on the staging directory (777). When upgrading the node to vCloud Connector 2.6, these permissions are incorrectly set to 755. This removes the write permission for other, which in this instance references the admin user.
For details and updates on this issue refer to KB article: Cannot access the transfer directory after upgrading to vCloud Connector 2.6 (2073208)
VMware has become aware of an issue where machines running vCenter Single Sign-On 5.5 running on Windows Server 2012 authenticating to an Active Directory Domain running on Windows Server 2012 will not be able to authenticate to Active Directory.
For further information and updates, please refer to KB article: Active Directory authentication fails when vCenter Single Sign-On 5.5 runs on Windows Server 2012 and the AD Domain Controller is also on Windows Server 2012 (2060901).
VMware has become aware of an issue where an upgrade to vSphere 5.5 may fail when upgrading the SSO component. The issue appears to be related to the default SSO certificate generated when installing vSphere 5.1 Build #799735
For details and updates on this issue refer to KB article: vSphere 5.5 Single Sign-On upgrade rolls back after importing Lookup Service data (2060511)
Location of Single Sign On log files for vCenter Server 5.1 (2033430)
VMware has become aware of an issue that may occur if you use Microsoft SQL Server 2005 SP4 as your vCloud Director database, you will not be able to successfully upgrade to (or do fresh install) vCloud Director 5.5.0
VMware is currently investigating this issue. The problem occurs only with the specific database version mentioned.
For more information and updates on this matter, reference Knowledgebase article: Unable to install or upgrade to VMware vCloud Director to version 5.5.0 when using SQL Server 2005 SP4 (2060068).
VMware has become aware of an issue that may occur after upgrading to vSphere Storage Appliance (VSA) Manager 5.5, wherein the VSA Manager plug-in does not appear in the vSphere Web Client.
- The VSA Manager plug-in does not appear in the vSphere Web Client
- You are unable to upgrade the VSA cluster service
For updates and further information on this restart issue, please refer to Knowledgebase article: After upgrading to vSphere Storage Appliance (VSA) Manager 5.5, the VSA Manager plug-in does not appear in the vSphere Web Client (2059473).
vSphere Replication in a vSphere 5.1 environment will fail after an automatic upgrade to vSphere Replication 5.5. A pre-release version of vSphere Replication 5.5 has been released and will be downloaded and installed if you have Automatic Check and Install Updates configured.
For more information about the issue, see the article linked below.
- vSphere Replication fails
- The vSphere Replication version now says 5.5 instead of 5.1
If you experience this issue, contact VMware Support.
To ensure you are not impacted by this issue:
- Log into the vSphere Replication Appliance.
- Click the Update tab.
- Click Settings.
- Choose No Automatic Updates.
vCenter Update Manager may also have this version downloaded. VMware recommends not installing the vSphere 5.5 Replication version in your 5.1 environment.
For more information, see this KB article: http://kb.vmware.com/kb/2060190
Due to a change in the support request file upload process, VMware Support Assistant 5.1 temporarily cannot be used to upload files. For more details, see knowledge base article: VMware Support Assistant 5.1 will fail to upload log files (2059759). Subscribe to the article to be notified when there are updates.
Support requests can still be filed through Support Assistant, but you must use a temporary manual FTP process to upload files to VMware Technical Support. To provide supporting information like log files, configuration files, and screenshots, follow the instructions in knowledge base article: Uploading diagnostic information for VMware (1008525).