VMware Cloud Foundation 220.127.116.11 | 26 OCTOBER 2017
Cloud Foundation 18.104.22.168 is a minor patch release, resulting in abbreviated release notes. The content of the Cloud Foundation 2.2 release notes applies to version 22.214.171.124 as well.
What's in the Release NotesThe release notes cover the following topics:
The VMware Cloud Foundation 126.96.36.199 is an update bundle release that upgrades both Lifecycle Manager (LCM) and VMware NSX for vSphere.
Cloud Foundation deploys the VMware SDDC Software Stack. For information about what is new in those products, as well as their known issues and resolved issues, see the release notes for those software versions. You can locate their release notes from their documentation landing pages at docs.vmware.com.
Installation and Upgrades Information
You can upgrade to Cloud Foundation 188.8.131.52 from a 184.108.40.206 deployment.
Supported Upgrade Paths
The following upgrade paths are supported in sequential manner:
- 2.2 to 220.127.116.11 to 18.104.22.168
LCM Upgrade Bundles
The Cloud Foundation 22.214.171.124 software BOM contains the VMware software components described in the table below. This patch bundle is hosted on the VMware Depot site and available via the Lifecycle Management feature in SDDC Manager. See Lifecycle Management in the Administering VMware Cloud Foundation guide.
|Software Component||Version||Date||Build Number|
|Lifecycle Manager (LCM)||2.2.1||26 OCTOBER 2017||6922936|
|VMware NSX for vSphere||6.3.4||26 OCTOBER 2017||6845891|
Before scheduling an upgrade, run the pre-check utility with the following command from the SDDC Manager Controller VM:
For more information on applying the patch bundle, see the following resources:
- Patching and Upgrading Cloud Foundation in the Administering VMware Cloud Foundation guide
- VMware Cloud Foundation 2.2 Release Notes: LCM Known Issues
- VMware Cloud Foundation 126.96.36.199 Release Notes
- NSX update may not appear to be available due to disconnected NSX controllers.
The NSX 6.3.3 controller node has a periodic clean-up task that deletes a status file required by the API server, if the API server has sufficiently low activity. As a result, workflows such as traceflow and central CLI will fail. If external events disrupt the persistent TCP connections between NSX Manager and controller, NSX Manager will lose the ability to make API connections to controllers, and the UI will display the controllers as disconnected. There is no datapath impact, but as a result, the NSX update bundle may not appear as available in the LCM Updates page.
Workaround: In SDDC Manager, go to the Lifecycle Management > Inventory page. Expand the domain and check if any domain displays a FAILED status.
If a domain is in a FAILED state:
- Open vSphere Web Client and go to Networking and Security > Installation.
- In the Installation page, click the Management tab, which displays the status of the NSX Controller nodes.
- If any NSX Controller shows as disconnected, see Knowledge Base article 2151719 for the procedure to resolve this issue.
NOTE: After resolving the controller issue, it may take several minutes for the NSX update bundle to become available in the Update page.
- Repeat the above steps in the vSphere Web Client to verify that all NSX controllers are now connected.
- Return to the Lifecycle Management > Update page to confirm that the NSX update bundle now appears as available.
- Out of sequence application of 188.8.131.52 bundles prevent application of 184.108.40.206 bundles on workload domain.
If a customer downloads both 220.127.116.11 and 18.104.22.168 bundles, and applies 22.214.171.124 bundles only to the Management domain, the 126.96.36.199 bundle shows as available and 188.8.131.52 bundles become unavailable for workload domains.
- If no updates have been applied yet, schedule 184.108.40.206 updates together for both Management and workload domains.
- If 220.127.116.11 bundles have been applied only to the Management domain, apply 18.104.22.168 Cloud Foundation bundles to the Management domain. The 22.214.171.124 bundles will then be available for workload domains.