VMware Cloud Foundation 2.3.2.1 Release Notes

VMware Cloud Foundation 2.3.2.1 | 20 JUL 2018 | Build 9151413

Cloud Foundation 2.3.2.1 is a minor patch release, resulting in abbreviated release notes. The contents of the Cloud Foundation 2.3, 2.3.1, and 2.3.2 release notes apply to version 2.3.2.1 as well.

What's in the Release Notes

The release notes cover the following topics:

Installation and Upgrade Information

You must upgrade to Cloud Foundation 2.3.2.1 from a 2.3.2 deployment. For instructions, see Patching and Upgrading Cloud Foundation in the Administering VMware Cloud Foundation document..

Cloud Foundation Upgrade Bundles

The Cloud Foundation 2.3.2.1 software BOM contains the VMware software components described in the table below. This upgrade and patch bundle is hosted on the VMware Depot site and available via the Lifecycle Management feature in SDDC Manager.

Software Component Version Date Build Number
ESXi 6.5 U2b/EP7 20 JUL 2018 8935087
VMware vCenter Server on vCenter Server Appliance 6.5 U2b/EP7 20 JUL 2018 8815520
VMware Cloud Foundation bundle 2.3.2.1 20 JUL 2018 9151413

Preparing for Upgrade

Before upgrading, perform the following tasks:

  1. Clean out out-of-date bundles. See Knowledge Base article 52402.
  2. Before scheduling an upgrade, run the pre-check utility with the following command from the SDDC Manager Controller VM:

    ./sos --pre-upgrade-check

Known Issues

  • SDDC Manager upgrade may fail due to ESXi configuration issue.

    As part of the Cloud Foundation upgrade, ESXi netdump is automatically configured on all hosts in the Cloud Foundation inventory. As a result, any issue with this configuration on ESXi, the upgrade process may be blocked.

    Workaround: Using SSH, log in as root to the affected host and perform the following steps:

    1. Run cat /etc/vmware/vpxa/vpxa.cfg and note the serverIp value. For example, <serverIp>172.18.63.6</serverIp>.
    2. Open the /etc/vmware/vpxa/vpxa.cfg file and make null the value. For example, <serverIp></serverIp>.
    3. Save and close the file.

      NOTE: Do not restart any services.

    4. From the SDDC Manager Dashboard, restart the failed update.
    5. After the update successfully complete, reopen the /etc/vmware/vpxa/vpxa.cfg file and restore the serverIp setting to its original value.
  • Switch backup process failing at Create Switch Backup File operation.

    Observed in HP Synergy deployments.

    Workaround: Skip the switch backup process by following this procedure:

    1. Log in as root to the SDDC Manager Controller VM.
    2. Create the /home/vrack/VMware/vRack/workflow.properties file.
      root@sddc-manager-controller [ /home/vrack/VMware/vRack ]# touch workflow.properties
    3. Edit the /home/vrack/VMware/vRack/workflow.properties file to include the following lines:
      vrm.workflow.skip.tasks=true
      vrm.workflow.skip.tasks.ids=Create Switch Backup File
    4. Save and close the properties file.
    5. Update permission of the properties file:
      root@sddc-manager-controller [ /home/vrack/VMware/vRack ]# chown vrack:users workflow.properties
    6. Retry the backup process.
  • Password rotation may fail because PRM hosts have wrong IP address for host.

    During bring-up, a new IP address is assigned to host, but this value is not updated in the database. As a result, password rotation fails on the affected host because the IP CMS is looking for an outdated IP address.
     

    Workaround: You can manually correct this issue as follows

    1. In the CMS, locate the task that failed.
    2. Manually edit the <ipAddress> node setting for that task to the current IP address for the PRM host.
    3. Restart the bring-up service with the following command: curl -X PATCH http://localhost:9080/bringup-app/bringup/sddcs/<UUID>.
    4. Resume the password rotation operation.

      All tasks should successfully complete.

  • Updated Update physical switch configuration fails due to broken LLDP configuration.

    After upgrading a physical switch configuration, LLDP information stops being reported by one or more hosts, which causes the ConfigureVlans API to fail. The following workflows may be affected by this change:

    • Deploy vRealize Automation workflow may fail at Configure VLAN task.
    • Deploy vRealize Operations Manager workflow may fail at Configure VLAN task.

     

    Workaround: Disable and re-enable LLDP on the affected switch.

    1. If the failure occurs during vRealize Operations deployment, run the command vim-cmd hostsvc/net/query_networkhint on the hosts in the management cluster.
      If the command returns null, perform steps 2-8 below.
      If the command returns the correct value, retry the workflow; it should succeed.
    2. In the vSphere Web Client, locate the switch (vCenter name > vRack name > Management Networks > switch name).
    3. Right-click the switch name and select Settings > Edit Settings.
    4. In the Edit Settings dialog box, click Advanced in the nav bar to the left.
    5. Disable LLDP by selecting {disabled) for the Type setting and click OK.
    6. Re-enable LLDP by returning to the Edit Settings dialog box and then the Advanced Settings panel.
    7. Reset Type to Link Layer Discovery Protocol and set Operation to Listen.
    8. Wait at least five minutes.

    LLDP traffic should restart on all servers.

  • ESXi upgrade fails at ESX_UPGRADE_VUM_FAILED_TO_ENABLE_DRS_RULES operation.

    ESXi upgrade fails at ESX_UPGRADE_VUM_FAILED_TO_ENABLE_DRS_RULES operation and the provided recommendation does not work.

    Workaround: You must disable HA at the cluster level and retry the update in LCM. For details, see the Knowledge Base article VMware Cloud Foundation Upgrade fails because of HA agent issues (51877).