Data Services Manager (DSM) 9.1 Supervisor Service Activation Fails with ReconcileFailed Error on "depot.kube-system.svc"
search cancel

Data Services Manager (DSM) 9.1 Supervisor Service Activation Fails with ReconcileFailed Error on "depot.kube-system.svc"

book

Article ID: 445006

calendar_today

Updated On:

Products

VMware Data Services Manager for VCF VMware Cloud Foundation

Issue/Introduction

When attempting to enable, register, or upgrade the Data Services Manager (DSM) 9.1 operator package within a vSphere with Tanzu environment, the Supervisor Service configuration fails.

  • The Supervisor Service state remains trapped in a perpetual Activating or Error lifecycle loop.
  • One of the following errors observed on the Supervisor under Configured Core Supervisor Services:

    Service: consumption-operator.dsm.vsphere.vmware.com

    Reason: ReconcileFailed

    Message: vendir: Error: Syncing directory '0':

    Syncing directory '.' with imgpkgBundle contents:

    Fetching image: Error while preparing a transport

    to talk with the registry: Unable to create round tripper:

    Get "https://depot.kube-system.svc/v2/": Forbidden

     

    Reason: ReconcileFailed. Message: vendir: Error: Syncing directory '0': Syncing directory '.' with imgpkgBundle contents: Fetching image: Error while preparing a transport to talk with the registry: Unable to create round tripper: Get "https://depot.kube-system.svc/v2/": dial tcp: lookup depot.kube-system.svc on 127.0.0.53:53: no such host

Environment

  • Platform: VCF 9.1
  • Solution: Data Services Manager (DSM) 9.1

Cause

By default, the master declarative package layout for the DSM 9.1 operator is hardcoded to interface with an internal registry endpoint: depot.kube-system.svc. If this internal Software Depot service is not initialized, is missing from the infrastructure topology, or cannot be resolved by the local node stub resolver ($127.0.0.53:53$), the kapp-controller daemon cannot locate the deployment bundle, causing the synchronization loop to time out.

Resolution

Broadcom is aware of this issue and actively working on a permanent fix in a future release.

If you are experiencing this specific deployment block within your environment, please open a case with Broadcom Support for further assistance and to apply the interim workaround.

Additional Information

Related Information

https://techdocs.broadcom.com/us/en/vmware-cis/dsm/data-services-manager/9-1/using-vmware-data-services-manager-with-vmware-cloud-foundation/using-as-a-provider/install-the-dsm-supervisor-service.html