License assignment fails with "Licenses could not be assigned to the selected vCenter Systems" error
search cancel

License assignment fails with "Licenses could not be assigned to the selected vCenter Systems" error

book

Article ID: 449286

calendar_today

Updated On:

Products

VCF Operations VMware vCenter Server

Issue/Introduction

  • An attempt to license vCenter after registration to the Business Service Console fails with the following error: Licenses could not be assigned to the selected vCenter Systems

  • The vCenter license is visible on the License Management page, and the integration test of the vCenter appliance completes successfully.

  • The Management adapter logs in the operations appliance report a Missing Entitlement Allocation Id error under /storage/log/vcops/log/ManagementAdapter.log:

    [Timestamp] ERROR ManagementAdapter 25429 [ops@#### threadId="225081" threadName="vcf-licensing-assign-6" instanceId="54"] [(54) com.vmware.adapter.management.components.licensing.vcf.H.A] - Error while assigning entitlement to VC: 5c48d99b-573c-d974-1586-############ at vcenter-01.example.com
    [Timestamp] ERROR ManagementAdapter [ID] [ops@#### threadId="####" threadName="vcf-licensing-assign-1" instanceId="54"] [(54) com.vmware.adapter.management.components.licensing.vcf.H.A] - Task 5c48d99b-573c-d974-1586-############:com.vmware.cis.license.subscription.entitlement.entitlements failed to assigning entitlement 5c48d99b-573c-d974-1586-############, task details: Info (com.vmware.cis.task.info) => {
        [...]
        status = FAILED,
        cancelable = false,
        error = InvalidArgument (com.vmware.vapi.std.errors.invalid_argument) => {
            messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => {
        id = unused.id,
        defaultMessage = Missing Entitlement Allocation Id.,
        args = [],
        params = ,
        localized = Missing Entitlement Allocation Id.
    }],
            data = ,
            errorType = INVALID_ARGUMENT

Environment

  • VCF Operations 9.0.0, 9.0.1, 9.0.2

  • vCenter Server 9.1

Cause

A compatibility issue occurs because vCenter Server operates on version 9.1 while the operations appliance operates on version 9.0.0.0. This discrepancy results in a conflict between the active licensing models.

Resolution

To resolve the incompatibility and align the license models, complete the following steps:

Option 1: 

Upgrade VCF Operations to a compatible release with vCenter: Updating your VCF Operations Software and Broadcom Compatibility Guide

Option 2:

  1. Deploy a new vCenter compatible with VCF Operations version and license model: vCenter Deployment and Setup
  2. Add a new vCenter account to VCF Operations for the new vCenter on 9.0.2 to integrate it between vCenter and VCF Operations: Configuring a vCenter Account in VCF Operations

Additional Information

Contact Broadcom Support