Unable to apply 8.x license to VCF component such as ESXi and vSAN in VCF 5
search cancel

Unable to apply 8.x license to VCF component such as ESXi and vSAN in VCF 5

book

Article ID: 323370

calendar_today

Updated On:

Products

VMware Cloud Foundation VMware Cloud Foundation 5.x VMware SDDC Manager / VCF Installer

Issue/Introduction

  • After upgrading to VCF 5, applying ESXi 8.0 and vSAN 8.0 licenses fails with the following message even though the license has capacity.

    License key has insufficient license

  • SDDC Manager calculates the available CPUs for the license based on the core calculation instead of the actual number of CPUs for the cluster.

  • Reviewing SDDC - /var/log/vmware/vcf/domainmanager/domainmanager.log: 
    ERROR [vcf_om,a7c1da8a73154461,c742] [c.v.e.s.o.model.error.ErrorFactory,pool-3-thread-15] [KDMN8M] FAILED_TO_VALIDATE_LICENSING_SPEC Failed to validate Licensing spec for domain with id ####-####-####-####-####.
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to validate Licensing spec for domain with id ####-####-####-####.
        at com.vmware.vcf.licensemanager.service.actions.ValidateLicensingSpecAction.execute(ValidateLicensingSpecAction.java:100)
        at com.vmware.vcf.licensemanager.service.actions.ValidateLicensingSpecAction.execute(ValidateLicensingSpecAction.java:34)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionState.invoke(FsmActionState.java:62)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:159)
        at com.vmware.evo.sddc.orchestrator.platform.action.FsmActionPlugin.invoke(FsmActionPlugin.java:144)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.invokeMethod(ProcessingTaskSubscriber.java:400)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.processTask(ProcessingTaskSubscriber.java:520)
        at com.vmware.evo.sddc.orchestrator.core.ProcessingTaskSubscriber.accept(ProcessingTaskSubscriber.java:124)
        at jdk.internal.reflect.GeneratedMethodAccessor1358.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at com.google.common.eventbus.Subscriber.invokeSubscriberMethod(Subscriber.java:88)
        at com.google.common.eventbus.Subscriber$1.run(Subscriber.java:73)
        at org.springframework.cloud.sleuth.instrument.async.TraceRunnable.run(TraceRunnable.java:64)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)
    
Caused by: com.vmware.vcf.licensemanager.common.exception.LicenseManagerException: License Key ####-####-####-#### has available CPU packages 0, but required CPU packages for hosts are 16.

Environment

VMware Cloud Foundation 5.x

Cause

In VCF 5.x, the SDDC Manager UI has an issue calculating the required units. In the UI, the CPU column and Available Quantity come from the cluster.capacity.cpu.numberOfCores property in the /v1/clusters API response. However, the total available quantity for the license comes from the licenseKey.licenseKeyUsage.total property of the /v1/license-keys API response.

Resolution

This warning is a cosmetic UI error and will not prevent licensing the components. This warning can be safely ignored.

  • Action: Proceed with applying the license key.

  • Expected Result: The SDDC will successfully trigger a background workflow to apply the license. Once this completes, any lingering warning banners will automatically disappear.

Powered by Wolken Software