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

Cluster fails to complete provisioning when using proxy with custom trust bundle

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • None
    • 4.19.0
    • HyperShift
    • None
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when you created a cluster with secure proxy enabled and the certificate configuration is set to `configuration.proxy.trustCA`, the cluster installation failed. Additionally, the OpenShift OAuth API server could not use the management cluster proxy to reach cloud APIs. With this release, fixes are in place to prevent these issues. (link:https://issues.redhat.com/browse/OCPBUGS-51050[*OCPBUGS-51050*])
      Show
      * Previously, when you created a cluster with secure proxy enabled and the certificate configuration is set to `configuration.proxy.trustCA`, the cluster installation failed. Additionally, the OpenShift OAuth API server could not use the management cluster proxy to reach cloud APIs. With this release, fixes are in place to prevent these issues. (link: https://issues.redhat.com/browse/OCPBUGS-51050 [* OCPBUGS-51050 *])
    • Bug Fix
    • Done

      Description of problem:

      When the cluster is created with a secure proxy enabled, and certificate is set in configuration.proxy.trustCA, the cluster fails to complete provisioning.
      4.19.0-0.nightly-2024-12-10-040415    

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

          

      How reproducible:

          always

      Steps to Reproduce:

          1. Create a cluster with a secure proxy, certificate is set in .spec.configuration.proxy.trustCA.
          3.
          

      Actual results:

          cluster does not complete provisioning

      Expected results:

          cluster completes

      Additional info:

          root cause is that certificate in additionalTrustBunlde isn't propagated into ingress proxy. 
      slack:
      https://redhat-internal.slack.com/archives/G01QS0P2F6W/p1734047816669079?thread_ts=1734023627.636019&cid=G01QS0P2F6W
      
      
      

              agarcial@redhat.com Alberto Garcia Lamela
              rhn-support-jiezhao Jie Zhao
              Jie Zhao Jie Zhao
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: