After VCF upgrade to 9.1, unable to license vCenter Server. Error: "Licenses could not be assigned to vCenters"

Products

• VCF Operations

Issue/Introduction

After VCF upgrade to 9.1, unable to license vCenter Server. Error: "Licenses could not be assigned to vCenters"

On the VCF Operations appliance, you can see log entries in /storage/log/vcops/log/adapters/ManagementAdapter/ManagementAdapter_XX.log : 

 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 = <null>,
    localized = Missing Entitlement Allocation Id.

From the VCF Operations appliance, you can query the vcopsdb and see a '9.0' product_family_version: 

First, connect to the database :

su - postgres -c "/opt/vmware/vpostgres/current/bin/psql -d vcopsdb -p 5433"


Then: 

SELECT vc_id, product_family, product_family_version FROM vcf_entitlement_vcenter_raw_usage;

(vc_id column has been redacted below)

Environment

VCF 9.1

Cause

Invalid '9.0' licensed components in the VC Database conflicting with applying the 9.1 license to vCenter. 

Resolution

Issue to be fixed in an upcoming version of VCF. 

To obtain a workaround, please file a case with Broadcom technical support.