VMware Cloud Foundation 4.2 | 09 FEB 2021 | Build 17559673
Check for additions and updates to these release notes.
The VMware Cloud Foundation (VCF) 4.2 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||4.2||09 FEB 2021||17559673|
|SDDC Manager||4.2||09 FEB 2021||17559673|
|VxRail Manager||7.0.131||23 FEB 2021||n/a|
|VMware vCenter Server Appliance||7.0 Update 1c||17 DEC 2020||17327517|
|VMware NSX-T Data Center||3.1.0||30 OCT 2020||17107167|
|VMware vRealize Suite Lifecycle Manager||8.2 Patch 2||04 FEB 2021||17513665|
|Workspace ONE Access||3.3.4||04 FEB 2021||17498518|
|vRealize Automation||8.2||06 OCT 2020||16980951|
|vRealize Log Insight||8.2||06 OCT 2020||16957702|
|vRealize Log Insight Content Pack for NSX-T||3.9.2||n/a||n/a|
|vRealize Log Insight Content Pack for Linux||2.1||n/a||n/a|
|vRealize Log Insight Content Pack for Linux - Systemd||1.0||n/a||n/a|
|vRealize Log Insight Content Pack for vRealize Suite Lifecycle Manager 8.0.1+||1.0.2||n/a||n/a|
|vRealize Log Insight Content Pack for VMware Identity Manager||2.0||n/a||n/a|
|vRealize Operations Manager||8.2||06 OCT 2020||16949153|
|vRealize Operations Management Pack for VMware Identity Manager||1.1||n/a||n/a|
The following documentation is available:
The following limitations apply to this release:
You can upgrade directly to 4.2 if your environment is at 4.1 or 220.127.116.11. If your environment is at a version earlier that 4.1, follow the process below to upgrade to 4.2:
After upgrading to SDDC Manager 4.2, the authentication mechanism for the Dell EMC depot changes from Basic Auth (V1 Auth) to NGSSO (V2 Auth). The underlying target URL has also changed to https://ssgosghop.emc.com. You must disconnect and reconnect to the Dell EMC depot to initialize this update. In the SDDC Manager UI, click Administration > Repository Settings and disconnect and then reconnect to the Dell EMC depot using sequential upgrade.
The following issues have been resolved:
VxRail component upgrade failed with error Auth Fail
VxRail component upgrade failed with error HostKey has been changed
Create NSX-T Data Center Transport Nodes from Discovered Nodessubtask
Management NIC does not have subnet mask, UNABLE_TO_RETRIEVE_HOST_ATTRIBUTES
For VMware Cloud Foundation 4.2 known issues, see VMware Cloud Foundation 4.2 Known Issues.
VMware Cloud Foundation 4.2 on Dell EMC VxRail known issues and limitations appear below:
After upgrading from VMware Cloud Foundation 4.1 with VxRail Manager 7.0.100, the VxRail Manager 7.0.131 bundle is not available
While upgrading from VMware Cloud Foundation 4.1 with VxRail Manager 7.0.100, you may not be able to download the required VxRail Manager 7.0.131 bundle.
Workaround: See KB 83029.
Upgrade to VMware Cloud Foundation on Dell EMC VxRail 4.2 failed for an AVN VxRail environment with a single vSphere Distributed Switch
When you upgrade an AVN VxRail environment with a single vSphere Distributed Switch, the upgrade fails because AVN specific VLAN port groups are missing from the SDDC Manager inventory.
curl 127.0.0.1/inventory/vds | json_pp
The command retrieves information on all vDSes available in the inventory and saves it in a JSON file (vds.json).
curl -X PUT -H "Content-Type:application/json" --data @vds-updated.json 127.0.0.1/inventory/vds/VDS_ID
curl -X PUT -H "Content-Type:application/json" --data @vds-updated.json 127.0.0.1/inventory/vds/203c9b5b-ad0d-4e69-88d2-1983a6235323
VxRail upgrade task in SDDC Manager displays incorrect status
The VxRail upgrade task status in SDDC Manager is displayed as running even after the upgrade is complete or failed.
Workaround: Restart the LCM service:
User name: vcf
Password: use the password specified in the deployment parameter workbook.
systemctl restart lcm
Task status is synchronized after approximately 10 minutes.
Host with upper case letters in its name fails to be added to SDDC Manager
Hosts with upper case letters in their names can be added successfully to a VxRail cluster, but cannot be added to SDDC Manager.
Workaround: Rename the host name to contain only lower case letters and then re-try the add host workflow.
vSphere Cluster Services (vCLS) VMs are moved to remote storage after a VxRail cluster with HCI Mesh storage is imported to VMware Cloud Foundation
When you configure HCI Mesh storage on a VxRail cluster and then import it to VMware Cloud Foundation, vCLS VMs are moved to the remote storage instead of being placed on the cluster's primary storage. This can result in errors when you unmount the remote storage for the cluster.
In the Hosts and Clusters tab, click the Cluster entity and check the URL.
The cluster morfId for this URL is 'domain-c10'.
Be default, vCLS property set to true:
Click Edit Settings, set the flag to 'false', and click Save.
Click Edit Settings, set the flag to 'true', and click Save.
Three vCLS VMs are displayed in the VMs and Templates tab.
vVols is not a supported storage option
Although VMware Cloud Foundation on Dell EMC VxRail does not support vVols, storage settings options related to vVols appear in the SDDC Manager UI. Do not use Administration > Storage Settings to add a VASA provider.
Workaround: See KB 81321 for information about how to remove the Storage Settings from the SDDC Manager UI.
The API does not support adding a host to a cluster with dead hosts or removing dead hosts from a cluster
The following flags appear in the API Reference Guide and API Explorer, but are not supported with VMware Cloud Foundation on Dell EMC VxRail.
forceHostAdditionInPresenceofDeadHosts: Use to add host to a cluster with dead hosts. Bypasses validation of disconnected hosts and vSAN cluster health.
forceByPassingSafeMinSize: Remove dead hosts from cluster, bypassing validations.
Adding a VxRail cluster with hosts spanning multiple racks to a workload domain fails
If you add hosts that span racks (use different VLANs for management, vSAN, and vMotion) to a VxRail cluster after you perform the VxRail first run, but before you add the VxRail cluster to a workload domain in SDDC Manager, the task fails.