Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-2810

timeout.Reconciliation setting not affecting polling frequency

XMLWordPrintable

    • 3
    • False
    • None
    • True
    • Hide
      Before this update, reconciliation timeout setting in the argocd-cm configmap was not being correctly applied to the controller. This update fixes the issue by reading and applying the reconciliation timeout settings from the argocd-cm configmap . Now, users can successfully modify the reconciliation timeout from the appSync setting.
      Show
      Before this update, reconciliation timeout setting in the argocd-cm configmap was not being correctly applied to the controller. This update fixes the issue by reading and applying the reconciliation timeout settings from the argocd-cm configmap . Now, users can successfully modify the reconciliation timeout from the appSync setting.
    • GITOPS Sprint 241

      Description of problem:

      When setting the timeout.reconciliation in the argocd-cm, the frequency in which an application syncs does not change from the default 3 minutes even when the repo server pod shows that the value is the expected one that was set. 

      Issue in Argo CD upstream: https://github.com/argoproj/argo-cd/issues/11995 

      Conversation on slack about this issue: https://redhat-internal.slack.com/archives/CMP95ST2N/p1680883835408519 

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. start an argocd instance
      2. set timeout.reconciliation: 1d in argocd-cm
      3. {}restart every Deployment and the argocd-applicaton-controller.

      Actual results:

      1. look at the logs of the application controller and you will notice that the app still syncs every 3 minutes instead of the set value. 

      Expected results:

      1. The controller should sync every x set value instead of the default 3 minutes. 

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Acceptance criteria: 

      • Review the PR
      • Get the PR merged
      • Get the changes into GitOps operator.

      Definition of Done:

      • Acceptance criteria is met. Code is submitted, tested, and merged.

      Build Details:

      According to issue thread on argocd github, the problem is happening as far back as v2.3

      Additional info (Such as Logs, Screenshots, etc):

            Unassigned Unassigned
            rescott1 Regina Scott
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: