Unable to register Supervisor Cluster with error "API Error: Failed to register management cluster with configurations: Internal Server Error: please try again later (internal error)" in step 2 in Tanzu Mission Control Self-Managed 1.4.2.
search cancel

Unable to register Supervisor Cluster with error "API Error: Failed to register management cluster with configurations: Internal Server Error: please try again later (internal error)" in step 2 in Tanzu Mission Control Self-Managed 1.4.2.

book

Article ID: 418009

calendar_today

Updated On:

Products

VMware Tanzu Mission Control

Issue/Introduction

Unable to register the Supervisor Cluster with below error after Step 2 in Tanzu Mission Control Self-Managed 1.4.2.

In cluster-agent logs, we see the error below.

{"component":"server-serve-grpc","error":"<harbor_repository>/tmc-sm/tap-tmc-docker-virtual.usw1.packages.broadcom.com/extensions/tmc-bootstrapper/supervisor/manifest:20250609161419230-2a1e223a256b31a12a6b294df6011b8ff7c88f31 was not fetched: could not load image source: get image from the registry: GET https://<harbor_repository>/v2/tmc-sm/tap-tmc-docker-virtual.usw1.packages.broadcom.com/extensions/tmc-bootstrapper/supervisor/manifest/manifests/20250609161419230-2a1e223a256b31a12a6b294df6011b8ff7c88f31:
NOT_FOUND: repository tmc-sm/tap-tmc-docker-virtual.usw1.packages.broadcom.com/extensions/tmc-bootstrapper/supervisor/manifest notfound","grpc.method":"Create","grpc.service":"vmware.tanzu.manage.v1alpha1.managementcluster.ManagementClusterResourceService","grpc.start_time":"YYYY-MM-DDTXX:XX:XXZ","level":"error","msg":"failed to get spec for tmc-bootstrapper","peer.address":"X.X.X.X:36252","request-id":"c37f8b3f-a235-4b4d-9163-3a1af6a1076d","request.kind":"unary","span.kind":"server","subcomponent":"requests","system":"grpc","time":"YYYY-MM-DDTXX:XX:XXZ","uid":"917c4179-2a1f-466d-96b6-a7acd2a79aa7"}

Verify from Harbor, tmc-sm project that the mentioned image "tap-tmc-docker-virtual.usw1.packages.broadcom.com/extensions/tmc-bootstrapper/supervisor/manifest" is not present.

Environment

Tanzu Mission Control Self-Managed version 1.4.2

Cause

Images are not correctly pushed to the Harbor project tmc-sm.

Resolution

1. Try downloading the TMC installer from Broadcom Support portal again.

  • Download, extract, and stage the installer for Tanzu Mission Control Self-Managed.
  • Download the installer for the version you want from Broadcom Support.
  • Create a directory on the bootstrap computer and extract the tarball into the directory. For example:
  • mkdir tanzumc
    tar -xf tmc-self-managed-1.4.3.tar -C ./tanzumc

2. Push the images to the registry by running:

./tmc-sm push-images harbor --project "<harbor_registory>/tmc-sm" --username "${HARBOR_USERNAME}" --password "${HARBOR_PASSWORD}" --concurrency 10 --package-repository-info=/dev/stdout

3. Restart the cluster-agent-service-server deployment in the tmc-local namespace.

kubectl -n tmc-local rollout restart deploy cluster-agent-service-server

Additional Information

For more information on installing Tanzu Mission Control Self-Managed 1.4, refer to the documentation below.

https://techdocs.broadcom.com/us/en/vmware-tanzu/standalone-components/tanzu-mission-control/1-4/tanzu-mission-control-documentation/tanzumc-sm-install-config-about-install-tmc-sm.html