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

Issue with GitOps Server after a ROSA HIbernate

XMLWordPrintable

    • False
    • None
    • False
    • Hide
      Before this update, when a ROSA cluster with GitOps Operator installed and having an ArgoCD instance with dex based SSO configuration, when the cluster resumes back from an hibernation, it was not possible to login to the ArgoCD web console UI and the login screen would report an error about invalid redirect URI configured in the Dex configuration. This update fixes the issue by having the right dex redirect url updated in the ArgoCD configuration every time the ArgoCD server route is updated.
      Show
      Before this update, when a ROSA cluster with GitOps Operator installed and having an ArgoCD instance with dex based SSO configuration, when the cluster resumes back from an hibernation, it was not possible to login to the ArgoCD web console UI and the login screen would report an error about invalid redirect URI configured in the Dex configuration. This update fixes the issue by having the right dex redirect url updated in the ArgoCD configuration every time the ArgoCD server route is updated.

      Description of problem:

          After a ROSA clsuter comes out of hibernate we are unable to login to our Gitops instances if they are using Openshift as the backing SSO

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

          4.14+

      How reproducible:

      Hibernate a cluster with gitops and attempt to login to the gitops instance on wake up

      Steps to Reproduce:

          1.
    2.
    3.

      Actual results:

      Failed to query provider "https://openshift-gitops-server-openshift-gitops.apps.rhsaia.vg6c.p1.openshiftapps.com/api/dex": oidc: issuer did not match the issuer returned by provider, expected "https://openshift-gitops-server-openshift-gitops.apps.rhsaia.vg6c.p1.openshiftapps.com/api/dex" got "https://openshift-gitops-server/api/dex"

So somehow the clusters domain information is not being populated

      Expected results:

      Successful Login

      Additional info:

        Did some digging and the issue is the `argocd-cm` is not be populated correctly with the url. But it can be fixed by restarting the `openshift-gitops-operator-controller-manager` pod in the `openshift-gitops-operator` namespace then the `openshift-gitops-dex-server` and `openshift-gitops-server` pods in the `openshift-gitops` namespace

        1. ScreenShot 2024-04-26 at 08.16.42@2x.png
          448 kB
          Anupam Sengupta

            rh-ee-anjoseph Anand Francis Joseph
            jland@redhat.com James Land
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: