Configuration drift error after updating VSAN/Witness service tags on vmknic in vSphere Configuration Profiles

Products

• VMware vCenter Server 8.0
• VMware vSphere ESXi 8.0

Issue/Introduction

Configuration drift Pre-check errors are returned in vSphere Configuration Profiles (VCP) for following scenarios :

• Case-1: VCP Remediation workflow to remove existing vmknics with enabled service tags 'vsan', 'witness', 'vsan_external' from hosts in the cluster.
• Case-2: VCP Remediation workflow to add or remove enabled service tag 'vsan', 'witness', 'vsan_external' from existing vmknics on the hosts in the cluster.

Environment

vSphere 8.0 U2 or later with VCP enabled.

Cause

The VCP platform currently does not support VSAN configuration. VSAN configuration in VCP managed cluster is performed using existing VSAN API. However, these VSAN APIs internally modify vmknic networking configuration which is managed by VCP desired configuration document. The VCP framework does not remediate VSAN related networking drift since this might break the VSAN cluster.

Resolution

This is a known issue with vSphere 8.0 U2 or above, currently there is no resolution.

Workaround:

Manually edit vmknic configuration to enable the 'vsan', 'witness', 'vsan_external' traffic checkbox for each host through the VC UI to fix the Precheck error and continue with remediation workflow in VCP UI.