VMware Cloud Foundation 3.10 | 26 MAY 2020 | Build 16223257 VMware Cloud Foundation 3.10.0.1 on Dell EMC VxRail | 02 JUL 2020 | Build 16419449 Check for additions and updates to these release notes. |
The VMware Cloud Foundation (VCF) 3.10 on Dell EMC VxRail release includes the following:
The VMware Cloud Foundation software product is comprised of the following software Bill-of-Materials (BOM). The components in the BOM are interoperable and compatible.
VMware Response to Apache Log4j Remote Code Execution Vulnerability: VMware Cloud Foundation is impacted by CVE-2021-44228, and CVE-2021-45046 as described in VMSA-2021-0028. To remediate these issues, see Workaround instructions to address CVE-2021-44228 & CVE-2021-45046 in VMware Cloud Foundation (KB 87095).
Software Component | Version | Date | Build Number |
---|---|---|---|
Cloud Builder VM | 2.2.2.0 | 26 MAY 2020 | 16223257 |
SDDC Manager | 3.10 | 26 MAY 2020 | 16223257 |
VxRail Manager | 4.7.410 | 17 DEC 2019 | n/a |
VMware vCenter Server Appliance | 6.7 P02 / U3g | 28 APR 2020 | 16046470 |
VMware NSX Data Center for vSphere | 6.4.6 | 10 OCT 2019 | 14819921 |
VMware NSX-T Data Center | 2.5.1 | 19 DEC 2019 | 15314288 |
VMware Enterprise PKS | 1.7 | 02 APR 2020 | 16116522 |
VMware vRealize Suite Lifecycle Manager | 2.1 Patch 2 | 04 MAY 2020 | 16154511 |
VMware vRealize Log Insight | 4.8 | 11 APR 2019 | 13036238 |
vRealize Log Insight Content Pack for NSX for vSphere | 3.9 | n/a | n/a |
vRealize Log Insight Content Pack for Linux | 2.0.1 | n/a | n/a |
vRealize Log Insight Content Pack for vRealize Automation 7.5+ | 1.0 | n/a | n/a |
vRealize Log Insight Content Pack for vRealize Orchestrator 7.0.1+ | 2.1 | n/a | n/a |
vRealize Log insight Content Pack for NSX-T | 3.8.2 | n/a | n/a |
vSAN content pack for Log Insight | 2.2 | n/a | n/a |
vRealize Operations Manager | 7.5 | 11 APR 2019 | 13165949 |
vRealize Automation | 7.6 | 11 APR 2019 | 13027280 |
Horizon 7 | 7.10.0 | 17 SEP 2019 | 14584133 |
Note:
The following documentation is available:
VMware Cloud Foundation 3.10.0.1 on Dell EMC VxRail was released on 02 JUL 2020. You can upgrade to VMware Cloud Foundation 3.10.0.1 from a 3.10 deployment, or you can use the skip-level upgrade tool to upgrade to VMware Cloud Foundation 3.10.0.1 from versions earlier than 3.10.
VMware Cloud Foundation 3.10.0.1 contains the following BOM updates:
Software Component | Version | Date | Build Number |
---|---|---|---|
SDDC Manager | 3.10.0.1 | 30 JUN 2020 | 16419449 |
VxRail Manager | 4.7.511 | 23 JUN 2020 | n/a |
VMware vCenter Server Appliance | 6.7 U3h | 28 MAY 2020 | 16275304 |
Note: VMware vSphere (ESXi) and VMware vSAN are part of the VxRail BOM. For more information, see Dell EMC VxRail documentation.
SDDC Manager 3.10.0.1 addresses the following:
SDDC Manager 3.10.0.1 contains security fixes for Photon OS packages PHSA-2020-3.0-0086 to PHSA-2020-3.0-0103 published here: https://github.com/vmware/photon/wiki/Security-Advisories-3
VMware vCenter Server Appliance 6.7 U3h addresses the following:
Security fixes for Photon OS packages.
The following issues have been resolved in VMware Cloud Foundation 3.10:
For VMware Cloud Foundation 3.10 known issues, see VMware Cloud Foundation 3.10 known issues.
VMware Cloud Foundation 3.10 on Dell EMC VxRail known issues and limitations appear below:
VMware Cloud Foundation on Dell EMC VxRail bring-up fails with error Failed to apply default vSAN policy
If bring-up fails when deploying the second Platform Services Controller (psc-2), retrying bring-up will fail with the error Failed to apply default vSAN policy
. The cause is that the original deployment of psc-2 was not removed from the vCenter Server inventory.
Workaround:
Bring-up fails with a password error
Bring-up fails with the error password must contain only alphanumerics and special characters
. The error is the result of different password requirements for VxRail and VMware Cloud Foundation.
Workaround: Make sure that VxRail clusters use passwords that meet the Cloud Foundation requirements for the following users:
Workload domain cannot be deployed on a fresh deployment of VMware Cloud Foundation on Dell EMC VxRail
The VxRail version 4.7.410 included in the 3.10 BOM deploys a vCenter Server that is incompatible with VMware Cloud Foundation 3.10. vCenter Server must be upgraded before deploying a workload domain.
Workaround:
Deleting a cluster from an NSX-T workload domain fails
If multiple clusters in the workload domain have similar names, deleting one of the clusters can fail with the error Can't find the TransportNodeProfile for the Cluster: <cluster name>
.
Workaround:
If you use the special character underscore (_) in the vCenter host name for the workload domain create operation, the vCenter deployment fails.
The vCenter deployment fails with the "ERROR > Section 'new_vcsa', subsection 'network', property 'system_name' validation
" error message.
Workaround: None. This is an issue in the vCenter product installer where the installer pre-validation fails. You should create the workload domain by providing valid vCenter host names.
The VxRail vCenter Plugin UI options may disappear after the OpenSSL/Microsoft certificate replace operations of all the components or just VxRail Manager.
The certificate replace operation involves changes in VxRail Manager and the vCenter VMs. Sometimes the vCenter plugin download might fail as the communication can happen with invalid thumbprint and the VxRail plugin UI option might disappear from vCenter. As a result, the user cannot invoke the add hosts and the remove hosts operations from vCenter.
Workaround: Reload the plugin by opening the VxRail Manager page which redirects to vCenter and make sure the VxRail UI options are visible in the vCenter UI.
Duplicate node expansion tasks are generated in SDDC Manager
If you select two hosts in the Add Host wizard, two tasks are generated and displayed in the task bar. The second task fails right away, but the first task adds both hosts.
Workaround: None. Ignore the failed task since the functionality is not impacted.
Cluster and/or domain deletion fails when cluster names are not unique across shared NSX-T workload domains
Cluster deletion fails when a cluster with the same name is present in another shared NSX-T workload domain. When two or more clusters have the same name, the associated NST-T workload domain cannot be deleted either.
Workaround:
Gateway timeout 504 error displayed during VxRail bundle upload
VxRail bundle upload fails with the 504 Gateway Time-out error.
Workaround:
155 location /lcm/ {
156 proxy_read_timeout 600;
157 proxy_connect_timeout 600;
159 proxy_pass http://127.0.0.1:7400;
160 }
systemctl restart nginx
Cancelling an in-progress VxRail upgrade displays an error
VxRail does not support cancellation of an in-progress upgrade though the UI provides this option.
Workaround: None.
Management VMs are unavailable in AZ2 when AZ1 is down
When you have a stretched cluster on the management domain and Availability Zone 1 (AZ1) goes down, if the L2 management network is not stretched you will not be able to manage your environment until AZ1 is back online. Although the management VMs are available on Availability Zone 2 (AZ2), their port groups are not configured correctly and the VMs cannot be accessed.
Workaround: None. You must wait until AZ1 is back online to access the management VMs.