Workload domain creation task fails with LICENSE_INSUFFICIENT_CAPACITY.
Article ID: 318230
Updated On:
Products
VMware Cloud Foundation
Issue/Introduction
This is a false positive and there is actually no issue with the license capacity.
Symptoms:
Workload domain creation fails at task "Validate Workload Domain Deployment Specification" with "PUBLIC_DOMAINSPEC_VALIDATION_FAIL". The error in the domainmanager.log looks like:
domainmanager.log
[YYYY-MM-DDTHH:MM:SS] ERROR [vcf_dm,0113f591ae534a6d,7287] [c.v.v.v.f.a.ValidateDomainSpecAction,dm-exec-19] Domain Spec validation failed with errors [LICENSE_INSUFFICIENT_CAPACITY]
[YYYY-MM-DDTHH:MM:SS] ERROR [vcf_dm,0113f591ae534a6d,7287] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-19] [71SSU2] PUBLIC_DOMAINSPEC_VALIDATION_FAIL
ED Failed to validate domain spec
com.vmware.evo.sddc.common.core.error.CompositeInvalidInputException: Failed to validate domain spec
at com.vmware.vcf.vimanager.fsm.actions.ValidateDomainSpecAction.execute(ValidateDomainSpecAction.java:61)
at com.vmware.vcf.vimanager.fsm.actions.ValidateDomainSpecAction.execute(ValidateDomainSpecAction.java:29)
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)
This error is seen when the capacity of the provided license for either vSphere or vCenter is less than 2x the requirement. For example, if the provided ESXi Hosts for workload domain creation require 24 CPU packages from the vSphere license and there are less than 48 CPU packages available in the provided vSphere license.
Environment
VMware Cloud Foundation 5.0
Cause
This is due to a bug in the validation code which doubles the license requirement for a vSphere or vCenter license.
Resolution
The issue has been resolved in VCF 5.0.0.1 release.
Workaround:
There are 2 approaches are mentioned below:
Workaround:
There are 2 approaches are mentioned below:
1. Provide a vSphere or/and vCenter Server license with larger capacity that can accommodate 2x the requirements of the ESXi Hosts or/and vCenter Servers.
2. If the reported insufficient license capacity issue is regarding the vSphere license, the license can be pre-applied on the ESXi Hosts that are to be used for the workload domain creation. After they are applied on the ESXi Hosts themselves, the workload domain creation should be started via the API endpoint POST "https://<sddc-manager-fqdn>/v1/domains" and not add license key on the ESXi Hosts inside the spec.
3. If the domain to be created has a number of ESXi Hosts which is 2x the minimum requirement of ESXi Hosts for domain creation, the domain can be created with a smaller number of hosts and then once successfully created, it can be expanded by adding the remaining number of hosts. For example, if the target domain is to have 12 ESXi Hosts, it can be initially created with 6 ESXi Hosts and once the domain creation is completed, the default cluster can be expanded by adding the remaining 6 ESXi Hosts to have the domain in the initial desired state.
2. If the reported insufficient license capacity issue is regarding the vSphere license, the license can be pre-applied on the ESXi Hosts that are to be used for the workload domain creation. After they are applied on the ESXi Hosts themselves, the workload domain creation should be started via the API endpoint POST "https://<sddc-manager-fqdn>/v1/domains" and not add license key on the ESXi Hosts inside the spec.
3. If the domain to be created has a number of ESXi Hosts which is 2x the minimum requirement of ESXi Hosts for domain creation, the domain can be created with a smaller number of hosts and then once successfully created, it can be expanded by adding the remaining number of hosts. For example, if the target domain is to have 12 ESXi Hosts, it can be initially created with 6 ESXi Hosts and once the domain creation is completed, the default cluster can be expanded by adding the remaining 6 ESXi Hosts to have the domain in the initial desired state.
Feedback
Yes
No
Powered by
