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

TLS handshake error observed for several operators

XMLWordPrintable

    • No
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      cluster is healthy. Observed below errors in cluster-node-tuning-operator pod.  
      ~~~
      2023/04/12 07:01:34 http: TLS handshake error from 10.129.0.29:37450: remote error: tls: bad certificate
      2023/04/12 07:01:35 http: TLS handshake error from 10.129.0.29:37464: remote error: tls: bad certificate
      2023/04/12 07:01:37 http: TLS handshake error from 10.129.0.29:37474: remote error: tls: bad certificate
      2023/04/12 07:04:34 http: TLS handshake error from 10.129.0.29:43390: remote error: tls: bad certificate
      ~~~
      From above logs I understand operator is not able to communicate to kube-apiserver-operator.
      ~~~
      openshift-kube-apiserver-operator                 kube-apiserver-operator-56bb44cf7-97kt7                          1/1    Running    0         7d     10.129.0.29    master02-sc.ipa.derfe.ine.mx
      ~~~
      Observed a lot of below certificate errors in openshift-kube-apiserver-operator pod:
      ~~~
      2023-04-11T18:03:38.533385853-06:00 E0412 00:03:38.533310       1 degraded_webhook.go:128] x509: certificate signed by unknown authority
      ~~~
      Need to investigate cause of these errors.

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

       

      How reproducible:

       

      Steps to Reproduce:

      1.
      2.
      3.
      

      Actual results:

       

      Expected results:

       

      Additional info:

       

              lszaszki@redhat.com Lukasz Szaszkiewicz
              rhn-support-aksjadha Akshata Jadhav
              Liquan Cui Liquan Cui
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: