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

[Bug] KeyCloak pods fails to come up

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Critical Critical
    • None
    • None
    • None

      Description of problem:

      While enabling keycloak using below steps, the keycloak pod failed to come up with error "ERROR Please mount a tmpfs volume at: '/mnt/rh-sso' path.".

       

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

      Steps to Reproduce

      • Install gitops-operator using the latest IIB

       

      1. Remove dex configuration from ArgoCD CR
      $ oc -n openshift-gitops patch argocd openshift-gitops --type='json' -p='[{"op": "remove", "path": "/spec/sso" }]'
      
      2. Add to the ArgoCD CR : $ oc edit argocd -n openshift-gitops
      spec:
        extraConfig:
          oidc.tls.insecure.skip.verify: 'true' 
        sso:
          provider: keycloak
          keycloak:
            rootCA: "---BEGIN---END---"
      
      
      3. Restart argocd server pod
      $ oc rollout restart deployment.apps/openshift-gitops-server -n openshift-gitops 

       

       

      Actual results:

       

      • pod fails to come up 
        Image:          registry.redhat.io/rh-sso-7/sso76-openshift-rhel8@sha256:bfb2c1d64342542157f313e078d32a82297731faf37bc27e9b2a89eefe7ab487

       

      Events:
        Type     Reason          Age                   From               Message
        ----     ------          ----                  ----               -------
        Normal   Scheduled       7m22s                 default-scheduler  Successfully assigned openshift-gitops/keycloak-1-zclsm to ip-10-0-173-215.us-east-2.compute.internal
        Normal   AddedInterface  7m20s                 multus             Add eth0 [10.131.0.38/23] from openshift-sdn
        Normal   Pulled          7m3s                  kubelet            Successfully pulled image "registry.redhat.io/rh-sso-7/sso76-openshift-rhel8@sha256:bfb2c1d64342542157f313e078d32a82297731faf37bc27e9b2a89eefe7ab487" in 16.91517279s (16.915179282s including waiting)
        Normal   Created         5m37s (x2 over 7m3s)  kubelet            Created container keycloak
        Normal   Started         5m37s (x2 over 7m3s)  kubelet            Started container keycloak
        Normal   Pulled          5m37s                 kubelet            Successfully pulled image "registry.redhat.io/rh-sso-7/sso76-openshift-rhel8@sha256:bfb2c1d64342542157f313e078d32a82297731faf37bc27e9b2a89eefe7ab487" in 402.28904ms (402.296296ms including waiting)
        Warning  Unhealthy       4m12s (x8 over 6m2s)  kubelet            Readiness probe failed: INFO Creating a new DMR API probe netrc file.
      ^[[0;31mERROR Please mount a tmpfs volume at: '/mnt/rh-sso' path.^[[0m
        Normal   Killing    4m12s (x2 over 5m42s)  kubelet  Container keycloak failed liveness probe, will be restarted
        Normal   Pulling    4m7s (x3 over 7m20s)   kubelet  Pulling image "registry.redhat.io/rh-sso-7/sso76-openshift-rhel8@sha256:bfb2c1d64342542157f313e078d32a82297731faf37bc27e9b2a89eefe7ab487"
        Warning  Unhealthy  92s (x10 over 6m2s)    kubelet  Liveness probe failed: INFO Creating a new DMR API probe netrc file.
      ^[[0;31mERROR Please mount a tmpfs volume at: '/mnt/rh-sso' path.^[[0m 

       

       

      Expected results:

      Keycloak pods should be up and login using keycloak should be successful  

      Reproducibility (Always/Intermittent/Only Once): 

      Acceptance criteria: 

      • keycloak login should work successfully

      Definition of Done:

      • acceptance criteria should be completed 

        Build Details:

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

       

       *

              aveerama@redhat.com Abhishek Veeramalla (Inactive)
              rh-ee-ansingh Anand Singh
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: