Harbor OCI Repository Not Visible During CNF Instantiation

Products

• VMware Telco Cloud Automation

Issue/Introduction

When Harbor is added as a partner system hosting the required OCI artifacts, its OCI repositories do not appear for selection during CNF instantiation.

Environment

3.2

Cause

• This issue occurs in a specific TCA setup where the disableRepoExtensionGroup flag in the globalsettings database table is set to true.
• This setting disables the use of the extension-platform, which implements latest feature support for Harbor as a partner system in TCA.

Resolution

Enable the use of the extension-platform by setting the disableRepoExtensionGroup flag in globalsettings to false.

1. Authenticate Using the Sessions API. Run the following API request on TCA-CP appliances to generate an authorization token:
   curl -v --location --request POST 'https://<TCACP-IP>/hybridity/api/sessions' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data-raw '{
    "username": "<username-for-vcenter-for-tca-cp>",
    "password": "<password>"
}'
2. Update the Extension Platform Setting - Use the generated authorization token (x-hm-authorization) from the Sessions API response to run the following request:
   curl --location --request PUT 'https://<TCACP-IP>/admin/hybridity/api/global/settings/ExtensionPlatform/disableRepoExtensionGroup' \
--header 'x-hm-authorization: <copy-from-sessions-API-response-headers>' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data-raw '{
    "value": "false"
}'
3. Restart Helm Service
   1. Log in to the TCA-CP Appliance Manager UI (https://<TCACP-IP>:9443).
   2. Navigate to the Appliance Summary tab.
   3. Under Telco Cloud Automation Services, locate Helm Package Manager Service.
   4. Click the Restart button.

Harbor OCI repositories should now be visible during CNF instantiation.