Details
-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
-
False
-
None
-
False
Description
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
Attachments
Issue Links
- is related to
-
GITOPS-3736 UI not available: oidc: issuer did not match the issuer returned by provider,
- Release Pending
- links to
-
RHSA-2024:130830 Openshift GitOps 1.12.2 - Bug Fixes and Argo CD UI security update
-
RHSA-2024:130841 Openshift GitOps 1.11.4 - Bug Fixes and Argo CD UI security update
-
RHSA-2024:130842 Openshift GitOps 1.10.5 - Bug Fixes and Argo CD UI security update