Skip vMotion validation for VMware Cloud Foundation workflows where vMotion connectivity is actually successful.

Products

• VMware Cloud Foundation

Issue/Introduction

Symptoms:

• Validation that the ESXi hosts that are to be part of the Cluster have vMotion network connectivity fails During any of the following operations

  • Adding a host to an existing Cluster

  • Creating a Cluster

  • Creating a Workload Domain

  • Stretching a Cluster

• The vMotion connectivity is actually successful and can be manually confirmed. 

Cause

This was due to a conceptual issue of how it tests the vMotion network connectivity.

Resolution

Support for disabling this vMotion validation has been introduced, in a scenario where this issue is being faced with the validation through the workflow.

This should only be implemented after investigating why the validation has failed and come to a conclusion that the validation has failed due to an issue with the validation itself, not the actual vMotion network connectivity.

Workaround:

Important: This workaround is applicable for VCF 4.0.1.2, VCF 4.1.0.2, VCF 4.2 and onwards.

To skip the vMotion validation, please use the steps below.

1. Open a SSH session to the SSDC Manager VM and change to the root user

su -

2. Edit the application properties file of the domain manager application.

Based on the VCF version, the application properties file to edit is:
VCF 4.0.1.2: /opt/vmware/vcf/domainmanager/config/application-prod.properties
VCF 4.1.0.2: /opt/vmware/vcf/domainmanager/config/application-prod.properties
VCF 4.2 and forward: /etc/vmware/vcf/domainmanager/application.properties
and the content to append to that file is:

validation.disable.vmotion.connectivity.check=true

3. Restart the Domain Manager service

systemctl restart domainmanager 

4. After the workflow has been completed, re-enable the validation by setting the value to 'false'

validation.disable.vmotion.connectivity.check=false

5. Restart the Domain Manager service

systemctl restart domainmanager 

Note: If there is a failed vMotion validation task in an existing workflow, setting the property to true and restarting the domain manager service would allow for the workflow to be restarted and the vMotion validation task would be still visible in the list of tasks but any execution related with it would be skipped.

Additional Information

A similar workaround can be applied to vSAN connectivity validation as well using the following entry in application.properties:

validation.disable.vsan.connectivity.check=true