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

ROSA HCP: TLS for openshift.default.svc is not valid

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.14, 4.15
    • HyperShift
    • Moderate
    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      Get "https://openshift.default.svc/.well-known/oauth-authorization-server": tls: failed to verify certificate: x509: certificate is valid for localhost, kubernetes, kubernetes.default, kubernetes.default.svc, kubernetes.default.svc.cluster.local, kube-apiserver, kube-apiserver.ocm-production-2b0eqpjq13aaba19ncgajh1asp39602g-faldana-hcp.svc, kube-apiserver.ocm-production-2b0eqpjq13aaba19ncgajh1asp39602g-faldana-hcp.svc.cluster.local, api.faldana-hcp.rvvd.p3.openshiftapps.com, api.faldana-hcp.hypershift.local, not openshift.default.svc

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

          4.15.9

      How reproducible:

          stable

      Steps to Reproduce:

          Get "https://openshift.default.svc/.well-known/oauth-authorization-server"

      Actual results:

          x509: certificate is valid for ... kubernetes.default.svc ..., not openshift.default.svc

      Expected results:

          OK

      Additional info:

          Works fine with ROSA Classic.
      
      The context: customer is configuring access to the RHACS console via Openshift Auth Provider.
      
      Discussion:
      https://redhat-internal.slack.com/archives/C028JE84N59/p1715048866276889

            Unassigned Unassigned
            mipetrov@redhat.com Michaël Petrov
            Jie Zhao Jie Zhao
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: