Host Commission workflow in VCF 9 fails with error "[Applicable to skipped ESXi Hosts]Perform set of validations for current workflow"
search cancel

Host Commission workflow in VCF 9 fails with error "[Applicable to skipped ESXi Hosts]Perform set of validations for current workflow"

book

Article ID: 423908

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

  • Host Commission workflow in VCF 9 fails with error "[Applicable to skipped ESXi Hosts]Perform set of validations for current workflow"
  • Error Screenshot: 

  • Logs on SDDC Manager /var/log/vmware/vcf/operationsmanager/operationsmanager.log indicates connection failure as per below:

    YYYY-MM-DDThh:mm:ss DEBUG [vcf_om,695366898c2f4f6df0217b470d5fdfbe,5987] [c.v.vcf.assessment.sdk.LambdaService,pool-2-thread-15] DAY_N_GUARDRAILS check type HOST_COMMISSION a5ec13fa-a404-4d25-9b5b-8a0b94876dfa status is FAIL
    YYYY-MM-DDThh:mm:ss ERROR [vcf_om,695366898c2f4f6df0217b470d5fdfbe,5987] [c.v.vcf.assessment.sdk.LambdaService,pool-2-thread-15] Lambda task a5ec13fa-a404-4d25-9b5b-8a0b94876dfa failed due to {"errorCode":"ASSESSMENT_CANNOT_ADD_
    CONNECTION_WITH_CAUSE","arguments":["<nstmanager.fqdn>","<nstmanager.fqdn>"],"message":"Cannot connect to <nstmanager.fqdn> Cause: <nstmanager.fqdn>","cause":[{"type":"com.vmware.v
    api.client.exception.ConnectionException","message":"<nstmanager.fqdn>"},{"type":"java.net.UnknownHostException","message":"<nstmanager.fqdn>"}],"referenceToken":"LT59UH"}
    YYYY-MM-DDThh:mm:ss ERROR [vcf_om,695366898c2f4f6df0217b470d5fdfbe,5987] [c.v.v.a.s.AssessmentLambdaServiceClient,pool-2-thread-15] Encountered exception while executing guardrail validations
    java.lang.IllegalStateException: Failed to evaluate lambda class LambdaInputRest {
        checkSetType: DAY_N_GUARDRAILS
        domainIds: [da4d5631-130e-42fe-a78b-fe8a85ebd347]
        targets: [class CheckTargetRest {
            type: HOST_COMMISSION
            resourceId: da4d5631-130e-42fe-a78b-fe8a85ebd347
        }]
        forceRefresh: true
    }

Environment

VCF 9.x

Cause

The issue occurred due to an incorrect DNS configuration for the NSX-T Manager, which caused a “could not connect to NSX-T Manager” error during guardrail validation.

Resolution

Ensure that the DNS records for the NSX-T Manager FQDN are correctly configured to support both forward and reverse name resolution from SDDC Manager, VCF Operations and vCenter Server. If necessary, work with your internal DNS or network team to validate and correct the DNS configuration.

Additional Information