Assigning License to vCenter in VCF 9.1 fails with "License could not be assigned to vCenters"

Products

• VCF Operations

Issue/Introduction

• In VCF Operations (VCF OPS) 9.1, when the License Server is registered in Disconnected Mode, attempting to assign a license to vCenter in the VCF Operations UI shows the following error: 'License could not be assigned to vCenters.'
  
  
• Clicking Details shows the following message: 'vCenter is unable to resolve the license server host name. Ensure an A record and PTR are added to the DNS servers used by the vCenter.'
  
  
  
  
  
• The collector.log on VCF Operations may show the following error:
  
  /storage/log/vcops/log/collector.log
  
  YYYY-MM-DD:T:HH:MM:SS ERROR collector #### [ops@#### threadId="#### " threadName="vcf-licensing-assign-##"] [(##) com.vmware.adapter.management.components.licensing.vcf.EntitlementMutationManager.updateEntitlement] - Task #####-####-###-####-########:com.vmware.cis.license.subscription.entitlement.entitlements failed to assigning entitlement ######-####-###-####-######, task details: Info (com.vmware.cis.task.info) => {

   localized = Failed to get Entitlements [ ######-####-###-####-######,] from License Server [ ######-####-###-####-######,] with URL <License_Server_FQDN > with response [License Server returned unexpected status code: 503 and response Service Unavailable]
  
  
• License Server FQDN identified in these logs does not match the actual FQDN configured in the VCF 9.1 environment.

Environment

• VMware Cloud Foundation (VCF) 9.1
• VMware vSphere Foundation (VVF) 9.1

Cause

This issue occurs because the License Server FQDN registered in the Broadcom Business Service Console does not match the actual FQDN configured in the VCF 9.1 management services.  Because VCF management components are immutable post-deployment, this FQDN mismatch causes synchronization requests to fail, manifesting as HTTP 503 "Service Unavailable" errors during entitlement assignment.

Resolution

To resolve the registration mismatch, decommission the incorrectly registered License Server component from the Broadcom Business Service Console and re-register it using the correct FQDN:

1. Verify that your DNS server contains the correct A record and PTR record for the License Server FQDN and IP address
   
   • Verify the configuration by running: nslookup <license_server_fqdn>
2. Log in to the Broadcom Business Service Console.
3. Navigate to the registered license server entry and execute the Unregister operation.
4. Re-register VCF Operations to the VCF Business Service Console using the validated License Server FQDN. Reference  Register VCF Operations and Your License Server in Disconnected Mode