Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-21086

[Argo CD Upstream] Application operation from progressive sync do not have retries by default

XMLWordPrintable

    • Quality / Stability / Reliability
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Workload Mgmt Train 28 - 2
    • Moderate
    • None

      Description of problem:

      Application that is generated from ApplicationSet with RollingSync configuration never retried if error occurred and if template does not have retries configuration defined.

      From Argo CD upstream https://github.com/argoproj/argo-cd/issues/20428

       

      Note:

      See https://docs.google.com/document/d/1zTI4QVstD6VGS5gcXZXTuNk179RNwQXskara2L2ktmU/edit?usp=sharing

      for details on why we are making fixes to the Argo CD upstream Progressive Sync feature.

      Version-Release number of selected component (if applicable):

      How reproducible:Actual results:

      Expected results:

      Progressive sync uses same defaults for retries as regular application sync operation.

      Additional info:

      argocd: v2.12.4+27d1e64
      BuildDate: 2024-09-26T06:36:13Z
      GitCommit: 27d1e641b6ea99d9f4bf788c032aeaeefd782910
      GitTreeState: clean
      GoVersion: go1.22.4
      Compiler: gc
      Platform: linux/amd64

              ming@redhat.com Mike Ng
              ming@redhat.com Mike Ng
              Michael Brudnoy, Xiangjing Li
              David Huynh David Huynh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: