This issue may occur in one of the following scenarios:
1. vLCM Image validation may fail when creating or editing a vLCM composite image, with the error:
"The alternative image '<image name>' is not compatible with configuration of default image."
2. Assigning a composite image to a VCP enabled cluster may fail and cause a general system error.
3. When enabling VCP (vSphere Configuration Profiles) on an existing vLCM cluster with an attached composite image, there is an error:
"Cluster has incompatible software. The components and add-ons with configurations should be unchanged in the default and all the alternate images."
VMware vCenter Server 9.0
Cluster uses alternate images AND
Cluster is vSphere Configuration profiles enabled AND
Cluster has more than one image attached AND
One of the attached images has vendor Addon with vibs that have configuration schemas
This can happen when one or more alternate image/s contains any user component or Addon with VIB having the configuration schema, on a cluster managed with vSphere Configuration Profiles.
The composite image helps define multiple alternative images in a single image that vLCM can apply to different hosts in the cluster. However, vSphere Configuration Profiles solution does not allow the configuration schema to differ across the alternative images. Some user components or add-ons package unique configuration schemas, when this is specified in an alternative image, these schemas would not be present in the default image or other alternative images. So, the image validation will fail for composite image
This Issue has been fixed in version 9.0.1.0 and above.
Workaround:
Install the addon directly on the host (e.g. with esxcli) and not add it to the Image. This will show the cluster as not compliant.