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

Duplicate words in Console UI "See breakdown breakdown"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.17.z, 4.16.z, 4.18.z, 4.19.z, 4.20.z, 4.21.0
    • Management Console
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • All
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

          Duplicate words in Console UI "See breakdown breakdown"
      
      

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

          4.21 back to 4.16

      How reproducible:

          Every time

      Steps to Reproduce:

          1.Create a cluster with 8 core worker
          2.Cordon all but one worker
          3. Apply Pod to force alert in console
      
      apiVersion: v1
      kind: Pod
      metadata:
        name: examplex
        labels:
          app: httpd
        namespace: default
      spec:
        securityContext:
          runAsNonRoot: true
          seccompProfile:
            type: RuntimeDefault
        containers:
          - name: httpd
            resources:
              requests:
                memory: "128Mi"
                cpu: "7000m"
              limits:
                memory: "128Mi"
                cpu: "7000m"
            image: 'image-registry.openshift-image-registry.svc:5000/openshift/httpd:latest'
            ports:
              - containerPort: 8080
            securityContext:
              allowPrivilegeEscalation: false
              capabilities:
                drop:
                  - ALL
      
      Navigate to https://console-openshift-console.apps.test421.cp.fyre.ibm.com/k8s/cluster/nodes/worker1.test421.cp.fyre.ibm.com
      Click on Alert *The total CPU resource limit and amount requested by all pods on this node is approaching the node’s capacity. Pod performance may be throttled under high load, and new pods may not be schedulable.*     

      Actual results:

          See breakdown breakdown

      Expected results:

           See breakdown

      Additional info:

          Related to customer ping for name.

              cajieh Cyril Ajieh
              pbastide_rh Paul Bastide
              None
              None
              None
              None
              Red Hat Bugzilla Authorized
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: