agctl sync fails to sync helm charts error some data failed to sync, retrying
search cancel

agctl sync fails to sync helm charts error some data failed to sync, retrying

book

Article ID: 384702

calendar_today

Updated On:

Products

VMware Telco Cloud Automation

Issue/Introduction

  • agctl sync fails to sync helm charts error some data failed to sync, retrying
  • airgap-logs/airgap/ansible_sync_log 
    TASK [Add registry repo] *******************************************************
    fatal: [localhost]: FAILED! => {"changed": true, "cmd": "helm repo add --username=admin --password='####' registry https://FQDN/chartrepo/registry", "delta": "0:00:00.073307", "end": "2024-12-10 01:13:00.198771", "msg": "non-zero return code", "rc": 1, "start": "2024-12-10 01:13:00.125464", "stderr": "Error: looks like \"https://FQDN
    /chartrepo/registry\" is not a valid chart repository or cannot be reached: Get \"https://FQDN/chartrepo/registry/index.yaml\": Not Found", "stderr_lines": ["Error: looks like \"https://FQDN/chartrepo/registry\" is not a valid chart repository or cannot be reached: Get \"https://FQDN/chartrepo/registry/index.yaml\
    ": Not Found"], "stdout": "", "stdout_lines": []}
    TASK [debug] *******************************************************************
    ok: [localhost] => {"msg": "Some data failed to sync, retrying..."}
  • Attempt to  manual adding helm repo succeeded but failed on automation
    helm repo add --username=admin --password='#####' registry https://FQDN/chartrepo/registry

Environment

TCA 3.2

Cause

  • Airgap proxy settings are incorrect

no_proxy=172.17., localhost
https_proxy=http://127.0.0.1:8081
http_proxy=http://127.0.0.1:8081

Resolution

  1. Add the host's FQDN to “no proxy
  2. Perform agctl sync
  3. Verify 'Helm Charts synchronization