Unable to apply 8.x license to VCF component such as ESXI /VSAN in VCF 5
search cancel

Unable to apply 8.x license to VCF component such as ESXI /VSAN in VCF 5

book

Article ID: 323370

calendar_today

Updated On:

Products

VMware Cloud Foundation VMware Cloud Foundation 5.x VMware SDDC Manager

Issue/Introduction

  • After upgrading to VCF 5, applying vSAN8 and ESX8 licenses fails with error message: License key has insufficient license while the license has a capacity.
  • SDDC calculate available CPUs for license based on Cores calculation instead of the actually number of CPUs for the cluster.
  • Error in /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 XXXXX-XXXX-XXXX-XXXX-XXXXXX.
    com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Failed to validate Licensing spec for domain with id XXXXX-XXXX-XXXX-XXXX-XXXXXX.
            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 XXXXX-XXXXX-XXXXX-XXXXX-XXXXX has available CPU packages 0, but required CPU packages for hosts are 16.


Environment

VMware Cloud foundation 5.x

Cause

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

 

Resolution

Ignore the error and proceed with applying the license in which a workflow get triggered by SDDC to apply the license to the intended component and completes successfully. Any banners related to license i.e. some components need to have a license key assigned will clear out afterward.

 

Additional Information

Impact/Risks:

Issue is cosmetic to the UI and shouldn't prevent customers from applying the license to intended component.