Description of problem: Updating GitOps Operator to version 1.3.2 did not trigger the update of existing ArgoCD instances to version 2.1.8, they were stuck on 2.0.5. Only after manual including the namespaces where the existing instances are running in the variable ARGOCD_CLUSTER_CONFIG_NAMESPACES of the gitops-operator-controller-manager configuration, update was triggered and argoCD instances updated to 2.1.8. Version-Release number of selected component (if applicable): GitOps Operator 1.3.2 How reproducible: Install previous version of GitOps operator on OCP 4.8, create some ArgoCD instances, and update the operator to 1.3.2 Steps to Reproduce: 1.Install any previous version of GitOps operator 2.Create few ArgoCD instances 3.Upgrade GitOps operator to 1.3.2 Actual results: Existing ArgoCD instances are stuck with version 2.0.5 Expected results: ArogCD instances to be automatically upgraded to the current version - in this case 2.1.8 Additional info: Update triggered only after manual editing of gitops-operator-controller-manager configuration, by adding the relevant namespaces where ArgoCD instances are running to the ARGOCD_CLUSTER_CONFIG_NAMESPACES variable.
GitOps uses JIRA, not BZ. Porting this issue to JIRA [1]. @pbunev, please monitor the issue at [1]. (Also, please open future GitOps issues on JIRA.) Thank you for reporting it. [1] https://issues.redhat.com/browse/GITOPS-1790