Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-29386

Customizing the authentication url in ingress.config.openshift.io results in openshift-authentication pods going into CrashLoopBackOff and continually redeploying

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • 4.13
    • oauth-apiserver
    • None
    • Low
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      After adding a custom authentication 'componentRoute' to the 'ingress.config.openshift.io' resource, the 'oauth-openshift-...' pods in the 'openshift-authentication' go into CrashLoopBackOff.
      
      
      

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

      4.13

      How reproducible:

      Consistently

      Steps to Reproduce:

          1. Add a custom componentRoute for authentication in the ingress.config.openshift.io resource similar to the following:
      
      ---
      oc edit ingress.config.openshift.io cluster
      ...
        componentRoutes:
        - hostname: oauth.example.com
          name: oauth-openshift
          namespace: openshift-authentication
          servingCertKeyPairSecret:
            name: oauth-ssl2
      ---

      Actual results:

          openshift-authentication pods go into CrashLoopBackOff

      Expected results:

          Custom change would successfully be rolled out to all dependent pods.

      Additional info:

          

            slaznick@redhat.com Stanislav Láznička
            lstanton@redhat.com Luke Stanton
            Jianwei Hou Jianwei Hou
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: