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

[Bug] ImagePullBackOff while enabling keycloak

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Critical Critical
    • None
    • None
    • None

      Description of problem: 

      While enabling keycloak for 1.9.1 and 1.9.0, keycloak pod is not able to pull keycloak image.

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

      occuring on 1.9 and 1.9.1 RC

      Steps to Reproduce

      Remove dex configuration from ArgoCD CR
      $ oc -n openshift-gitops patch argocd openshift-gitops --type='json' -p='[

      {"op": "remove", "path": "/spec/sso" }

      ]'

      Add to the ArgoCD CR :

      $ oc edit argocd -n openshift-gitops 

      Add below snippet code 

      spec:
        extraConfig:
          oidc.tls.insecure.skip.verify: 'true' 
        sso:
          provider: keycloak
          keycloak:
            rootCA: "---BEGIN---END---" 

      Restart argocd server pod
      $ oc rollout restart deployment.apps/openshift-gitops-server -n openshift-gitops

       

      Actual results:

      Failing with ImagePullBackOff error 

      Back-off pulling image "registry.redhat.io/rh-sso-7/sso75-openshift-rhel8@sha256:d5829e880db4b82a50a4962d61ea148522a93644174931b256d7ad866eadcf40"

      Expected results:

      keycloak-1-deploy pod should be up without any error

      Reproducibility (Always/Intermittent/Only Once): always

      Acceptance criteria: 

      • KeyCloak pod should be up 
      • we should be able to log in using keyCloak sso 

      Definition of Done:
      **

      • Acceptance criteria are met

      Build Details:

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

      log:
      Back-off pulling image "registry.redhat.io/rh-sso-7/sso75-openshift-rhel8@sha256:d5829e880db4b82a50a4962d61ea148522a93644174931b256d7ad866eadcf40"

       *

              Unassigned Unassigned
              rh-ee-ansingh Anand Singh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: