ConfigProfiles-compliant cluster suddenly reports compliance issues after upgrading to post-ESXi 8.0 U1.

Products

• VMware vCenter Server

Issue/Introduction

This article clarifies why the ConfigProfiles-compliant cluster suddenly reports compliance issues after upgrading to post-ESXi 8.0 U1.

Symptoms:

Upgrading ESXi to post 8.0 U1 could cause compliance drift in specific configurations - SSH and Entropyd.

Environment

VMware vCenter Server 8.0.2

Cause

A few additional configurations have been integrated with ConfigurationProfiles in 8.0 U2. Previously, these were stored in sticky bit files and were not tracked by ConfiguratonProfiles. 

After an upgrade to 8.0 U2, ConfigurationProfiles newly starts tracking these configurations. This change could lead to compliance drift between the desired cluster configurations and the current configuration on the hosts.

Resolution

User intervention is required to fix the newly visible drift. Users could either manually add required entries to the desired configuration or use the 'Import From Host' workflow under Drafts UI to obtain the new configurations from all the hosts in the cluster and incorporate them into the desired configuration.

Workaround:
Currently, there is no workaround.