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

Instances of Argo CD that are created and managed-by OpenShift GitOps go OutOfSync

XMLWordPrintable

    • False
    • False
    • Hide
      **Under Fixed Issues section**

      Previously, if you set up a new namespace to be managed by a new instance of Argo CD, it would immediately be **Out Of Sync** due to the new roles and bindings that the Operator creates to manage that new namespace. This behavior is fixed. link:https://issues.redhat.com/browse/GITOPS-1384[GITOPS-1384]
      Show
      **Under Fixed Issues section** Previously, if you set up a new namespace to be managed by a new instance of Argo CD, it would immediately be **Out Of Sync** due to the new roles and bindings that the Operator creates to manage that new namespace. This behavior is fixed. link: https://issues.redhat.com/browse/GITOPS-1384 [ GITOPS-1384 ]

      This is an extension of GITOPS-1247

      Although GITOPS-1247 fixed the initial issue (any Argo CD instance created by the openshift-gitops Argo CD would immediately be "out of sync"), the same behaviour happens once you set a new namespace to be managed by the new Argo CD.

      Shorter version:

      • Install OpenShift GitOps
      • Use default Argo CD instance to create a new Argo CD insance (e.g developer-argocd)
      • The "Application" in openshift-gitops should be green (in sync).  The new Argo CD instance (in developer-gitops) is ready for developers to use.
      • A new namespace is created (e.g. developer-test) and it is labeled so that it is managed by "developer-gitops"
      • A few seconds later, the "Application" in openshift-gitops that managed the developer Argo CD is now "out of sync" due to the new roles and bindings that the operator creates to manage that new namespace.

       

      I've added some instructions to the end of my original test repo to show how to reproduce the issue.

      https://github.com/pittar-sandbox/gitops-1247

        1. 2021-09-27_11-17.png
          2021-09-27_11-17.png
          48 kB

            [GITOPS-1384] Instances of Argo CD that are created and managed-by OpenShift GitOps go OutOfSync

            Andrew Pitt added a comment -

            You guys are fast!

            Andrew Pitt added a comment - You guys are fast!

            Jann Fischer added a comment -

            Jann Fischer added a comment -

            Jann Fischer added a comment -

            Validated that this is fixed in v1.3 latest RC already.

            Jann Fischer added a comment - Validated that this is fixed in v1.3 latest RC already.

            Jann Fischer added a comment -

            I will validate above claim against a 1.3 RC build today.

            Jann Fischer added a comment - I will validate above claim against a 1.3 RC build today.

            Jann Fischer added a comment -

            After a little research, I think this has been fixed in the upstream operator already, and the fix will be included in v1.3: https://github.com/argoproj-labs/argocd-operator/pull/414

            Jann Fischer added a comment - After a little research, I think this has been fixed in the upstream operator already, and the fix will be included in v1.3: https://github.com/argoproj-labs/argocd-operator/pull/414

            Jann Fischer added a comment -

            Thanks a lot for the very easy reproduction steps. I could successfully verify this behavior.

            Jann Fischer added a comment - Thanks a lot for the very easy reproduction steps. I could successfully verify this behavior.

              jfischer@redhat.com Jann Fischer
              rhn-support-apitt Andrew Pitt
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: