SDDC Manager Create Workload Domain task fails at Remediate ESXi Host(s) to be Compliant with Cluster's Image with error 'VLCM_REMEDIATE_PERSONALITY_FAILED'

Products

• VMware SDDC Manager
• VMware Cloud Foundation

Issue/Introduction

Creating a Workload Domain fails at Remediate ESXi Host(s) to be Compliant with Cluster's Image with error 'VLCM_REMEDIATE_PERSONALITY_FAILED'. 

/var/log/vmware/vcf/domainmanager/domainmanager.log on the SDDC Manager reports below error stack:

YYYY-MM-DDTHH:MM:SS.568+0000 ERROR [vcf_dm,################################,63bf] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-##]  [6521V5] VLCM_REMEDIATE_PERSONALITY_FAILED Applying personality to cluster domain-### failed with error: ApplyStatus (com.vmware.esx.settings.clusters.software.apply_status) => {
    status = SKIPPED,
    progress = <null>,
    startTime = YYYY-MM-DDTHH:MM:SS351Z[GMT],
    endTime = YYYY-MM-DDTHH:MM:SS.765Z[GMT],
    notifications = Notifications (com.vmware.esx.settings.notifications) => {
        info = <null>,
        warnings = [Notification (com.vmware.esx.settings.notification) => {
    type = WARNING,
    id = com.vmware.vcIntegrity.lifecycle.scl.InteropBundleUpdateRequired,
    time = YYYY-MM-DDTHH:MM:SS.763Z[GMT],
    message = LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
        id = com.vmware.vcIntegrity.lifecycle.scl.InteropBundleUpdateRequired,
        defaultMessage = Software compatibility cannot be determined for release 9.0.0.0.24755229, 9.0.0.0.24755230. It can be either a security patch or an out-of-date compatibility data bunlde having timestamp YYYY-MM-DDTHH:MM:SS.181000. Firstly, please ensure the software compatibility data bundle is up-to-date. Please note that no software compatibility checks are performed on security patches.,
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Applying personality to cluster domain-c## failed with error: ApplyStatus (com.vmware.esx.settings.clusters.software.apply_status)  

/var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server.log on the vCenter server reports reports below error stack:

YYYY-MM-DDTHH:MM:SS.066Z error vmware-vum-server[24116] [Originator@6876 sub=ScanUtil opID=################################] [ScanUtil 999] Host scan task failed for host host-##
YYYY-MM-DDTHH:MM:SS.066Z error vmware-vum-server[24116] [Originator@6876 sub=com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask opID=################################] [ClusterScanTask, 905] Task:com.vmware.vcIntegrity.lifecycle.DesiredScanClusterTask ID:################################. Failed to get host : ESX.EXAMPLE.COM (host-##) image result. Errors : Error:
-->    com.vmware.vapi.std.errors.error
--> Messages:
-->    com.vmware.vcIntegrity.lifecycle.EsxImage.DepotConnectError<Failed to connect to depot: 'URL: 'http://VCENTER.EXAMPLE.COM:9084/vum/repository/hostupdate/__micro-depot__vendor-vmw__metadata-61__index__.xml' Error: '[Errno 104] Connection reset by peer''>
--> ;default compliance will be substituted.

 

 

 

Environment

VMware Cloud Foundation 9.0

Cause

This issue occurs when the vVol storage is configured, and access to the vVol VASA provider on port 1443 is blocked by an external firewall.

Resolution

Allow TCP Port 1443 for communication between the ESX 9.0 hosts and the vCenter in external firewall.