Error: CNF135001 failed to fetch chart in TCP 5.0 due to OCI repository separation
Article ID: 451001
Updated On:
Products
Issue/Introduction
AKO deployment fails during instantiation in Telco Cloud Platform (TCP) 5.0. This occurs because Harbor OCI registries require images and Helm charts to be stored in separate repository paths, preventing VMware Telco Cloud Automation (TCA) from automatically locating the chart artifact.
Symptoms:
- CNF instantiation fails with the following error in the TCA UI:
Grant request failed: Helm API failed: CNF135001: failed to fetch chart ako (version=#.#.#) from extensions platform using url https://<harbor-fqdn>/chartrepo/tcp-caas not a valid chart repository Grant request failed: Helm API failed: CNF135001: failed to fetch chart ako (version=#.#.#) | tls: failed to verify certificate: x509: certificate signed by unknown authority Grant request failed: Helm API failed: CNF135001: failed to fetch chart ako (version=#.#.#) expected 1 layer for a helm chart, but found 4 layers
Environment
Telco cloud platform: 5.0
Telco cloud automation: 3.x
VMware Avi Load Balancer (AKO) 1.13.3
Cause
In Harbor versions integrated with newer TCP releases, Harbor operates as an OCI-compliant registry. Calling traditional HTTP repository URLs (/chartrepo/) fails because the registry expects OCI protocol syntax. Additionally, if provenance files (.prov) or extra metadata are pushed with the chart, the artifact may contain multiple layers, while TCA expects a single layer.
Resolution
Steps:
Ensure the CSAR file is updated to match the correct AKO/NF version being deployed.
Use the new image and Helm chart for AKO.
Create a separate folder for the Helm chart when publishing to Harbor, as the new Harbor version does not support separation within the same project repository.
Specify the location of the Helm chart manually during the AKO NF deployment, rather than relying on the globally detected default TCA repository (which contains only the AKO image and not the Helm chart).
Feedback
