Workload domain creation fails on the vCenter: Configure LACP on VDS task in VMware Cloud Foundation 2.2.1 environments

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

• Workload domain creation fails or hangs on the vCenter: Configure LACP on VDS task.
• The vSphere Web Client shows that many, if not all, of the NICs on the ESXi hosts in the new workload domain are not under vRack-LAG (as seen on Networking, select the vDS, Configure, Topology).
• The Teaming and Failover policy for all portgroups on the new vDS show that vRack-LAG is Standby while uplink1-4 are Active.
• VMware Cloud Foundation was not upgraded from version 2.1.3b to 2.2.1.

Environment

VMware Cloud Foundation 2.2.x

Resolution

This issue is resolved in VMware Cloud Foundation 2.3.2.1.

Workaround:
Use the following steps to workaround this issue in VMware Cloud Foundation 2.2.x (only for environments that were not upgraded from version 2.1.3b to 2.2.1):

1. Download the attached 55814_vrm-vsphere-2.2.1-RELEASE.zip file.
2. Use a file transfer utility to copy the 55814_vrm-vsphere-2.2.1-RELEASE.zip file to the /tmp folder on the SDDC Manager Controller virtual machine.
3. Log in to the SDDC Manager Controller virtual machine as the root user.
4. Issue the scsclient command. The prompt will change to SCSCLI>.
5. Issue the following commands to stop the vrm service:

show -servicestate all
service -stop vrm

6. Type quit to exit the scsclient utility.
7. Issue the following command to stop the scs service:

systemctl stop scs

8. Issue the following commands to make a backup of the jar files that will be replaced:

cp -p /home/vrack/vrm/webapps/vrm-ui/WEB-INF/lib/vrm-iaas-2.2.1-RELEASE.jar /home/vrack/
cp -p /home/vrack/vrm/webapps/vrm-ui/WEB-INF/lib/vrm-vsphere-2.2.1-RELEASE.jar /home/vrack/

9. Issue the following command to extract the contents of the /tmp/55814_vrm-vsphere-2.2.1-RELEASE.zip file:

unzip -d /tmp/ /tmp/55814_vrm-vsphere-2.2.1-RELEASE.zip

10. Issue the following commands to copy the extracted files to the correct location and set the appropriate ownership and permissions:

cp /tmp/vrm-iaas-2.2.1-RELEASE.jar /home/vrack/vrm/webapps/vrm-ui/WEB-INF/lib/
cp /tmp/vrm-vsphere-2.2.1-RELEASE.jar /home/vrack/vrm/webapps/vrm-ui/WEB-INF/lib/
chmod 777 /home/vrack/vrm/webapps/vrm-ui/WEB-INF/lib/vrm-iaas-2.2.1-RELEASE.jar
chmod 777 /home/vrack/vrm/webapps/vrm-ui/WEB-INF/lib/vrm-vsphere-2.2.1-RELEASE.jar
chown vrack:users /home/vrack/vrm/webapps/vrm-ui/WEB-INF/lib/vrm-iaas-2.2.1-RELEASE.jar
chown vrack:users /home/vrack/vrm/webapps/vrm-ui/WEB-INF/lib/vrm-vsphere-2.2.1-RELEASE.jar

11. Issue the following command to start the scs service:

systemctl start scs

12. Issue the scsclient command. The prompt will change to SCSCLI>.
13. Issue the following commands to start the vrm service:

show -servicestate all
service -start vrm
show -servicestate all

Note: It may take several minutes for all services (with the exception of bringup-ui) to have a PROCESS STATE of running. Rerun the show -servicestate all as needed.

14. Type quit to exit the scsclient utility.

Note: The workload domain creation workflow can be started at this point.

Additional Information

Workload domain creation fails on the vCenter: Configure LACP on VDS task in VMware Cloud Foundation 2.2.1 environments upgraded from version 2.1.3b
Workload domain creation fails on the vCenter: Configure LACP on VDS task in VMware Cloud Foundation 2.3.2 environments​
How to manually complete the Configure LACP for VDS task during a VMware Cloud Foundation workload domain creation workflow