An SDDC deployment using Cloud Builder fails when enabling EVC due to an incorrect/incompatible EVC mode value.

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:
Automated implementation of the VMware Validated Design SDDC using the VMware Cloud Builder appliance fails with an error when using an incorrect input parameter value in the Deployment Parameters workbook to enable Enhanced vMotion Compatibility (EVC).

The host's CPU hardware does not support the cluster's current Enhanced vMotion Compatibility.

Initiating a retry option in the VMware Cloud Builder UI after manually changing the EVC mode to correct value in vCenter Server will also not resolve the issue. VMware Cloud Builder attempts to enable an EVC mode with the incorrect/incompatible value provided in JSON and the deployment will continue to fail. 

Environment

VMware Validated Design for Software-Defined Data Center (SDDC) 5.1.x
VMware Validated Design for Software-Defined Data Center (SDDC) 5.0.x

Cause

An incompatible EVC mode value is provided in the Deployment Parameters workbook used by VMware Cloud Builder.

Resolution

VMware Cloud Builder supports submitting a retry with updated values using the following steps

1. Open the Deployment Parameters .XLS file and update the EVC mode with a correct and compatible value.
2. Save the changes to the Deployment Parameters .XLS file.
3. Open a browser and go to the VMware Cloud Builder UI (e.g. https://sfo01cb01.sfo01.rainpole.local) and login.
4. On the Upload a Config File tab, select the Select Architecture Type from the drop-down, click Upload Config File, and select the updated Deployment Parameters .XLS file.
5. Click Yes to overwrite the existing JSON payload with updated configuration parameters.
6. Click Generate JSON to regenerate the JSON payload with the update configuration parameters.
7. Click the Deploy SDDC tab and select the update deployment configuration file.
8. Click the Run Results option to list the previous failed deployment.
9. Click RETRY to resume the deployment.

An updated .JSON file will be used by the retry of the workflow.