VxRail: vSphere Lifecycle Manager enablement fails due to NON_COMPLIANT for Base_image
Summary: If the VxRail cluster has been upgraded from version 4.5.x to 7.0.240 or later, users must upgrade to newer releases and enable vSphere Lifecycle Management (vLCM).
Symptoms
Starting from VxRail release 7.0.240, vSphere Lifecycle Manager (vLCM) is supported on VxRail clusters. If the VxRail cluster is upgraded from 4.5.x and an attempt to enable vLCM is made either through the VxRail UI or vCenter vLCM interface, the scan results show the ESXi base image is noncompliant and vLCM enablement validation cannot pass.
Scan results show that the cluster is noncompliant as below:
Cause
Per VMware feedback: Known ESXi issue when upgrading from 6.5.x to 7.0.2 (VxRail 4.5.x to 7.0.240) and later when using profile upgrade, the applied upgrade method is recommended.
Based on VxRail's investigation, the apply method removes customer-owned drivers from the host which is not recommended. Therefore, when enabling vLCM, the scan results show that the ESXi base image is noncompliant.
If ESXi is directly upgraded from 6.5.x to 7.0.2 or later this issue occurs. If ESXi is upgraded from 6.5.x to 7.0.2 or later, then upgraded to 7.0.3, the issue is not present and vLCM enablement works.
Resolution
- Cancel the vLCM enablement process at the moment.
- Proceed with a minor version upgrade to a later 7.0.x version.
- Enable vLCM again.