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

SNO detection should be on `controlPlaneTopology` rather than `infrastructureTopology`

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • 4.14, 4.15, 4.16
    • kube-apiserver
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      Single Node Openshift detection should be on `controlPlaneTopology` rather than `infrastructureTopology`  

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

      How reproducible:

      always

      Steps to Reproduce:

      Deploy cluster with: 

controlPlaneTopology: HighlyAvailable
infrastructureTopology: SingleReplica   

      Actual results:

      Cluster detected as SNO and alert for `ExtremelyHighIndividualControlPlaneCPU` contains query used for SNO

      Expected results:

      Cluster is not detected as SNO and the alert for `ExtremelyHighIndividualControlPlaneCPU` contains the correct query for a multi node controlplane

      Additional info:

      https://github.com/openshift/cluster-kube-apiserver-operator/blob/master/pkg/operator/highcpuusagealertcontroller/highcpuusagealert_controller.go#L69   

              Unassigned Unassigned
              rhn-support-nigsmith Nigel Smith
              None
              None
              Ke Wang Ke Wang
              None
              Votes:
              1 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: