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

unable to create hypershift-hosted cluster via cluster-bot

    XMLWordPrintable

Details

    • Important
    • No
    • SDN Sprint 246, SDN Sprint 247, SDN Sprint 248, SDN Sprint 249
    • 4
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      Upon debugging, nodes are stuck in NotReady state and CNI is not initialised on them.

      Seeing the following error log in cluster network operator 

      failed parsing certificate data from ConfigMap "openshift-service-ca.crt": failed to parse certificate PEM

      CNO operator logs: https://docs.google.com/document/d/1hor1r9ue4gnetkXm9mh8AKa7vm8zNBPhUQqWCbbnnUc/edit?usp=sharing

      This is happening on a management cluster that is configured to use legacy service CA's:

      $ oc get kubecontrollermanager/cluster -o yaml --as system:admin
      apiVersion: operator.openshift.io/v1
      kind: KubeControllerManager
      metadata:
        name: cluster
      spec:
        logLevel: Normal
        managementState: Managed
        operatorLogLevel: Normal
        unsupportedConfigOverrides: null
        useMoreSecureServiceCA: false 

      In newer clusters, useMoreSecureServiceCA is set to true.

      Attachments

        Issue Links

          Activity

            People

              pdiak@redhat.com Patryk Diak
              rh-ee-neyadav Neha Yadav
              He Liu He Liu
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: