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

Increase Max node limit for topology page to 200

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • 4.15.z
    • 4.15.z
    • Dev Console
    • None
    • No
    • ODC Sprint 3255
    • 1
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, the {product-title} web console *Topology* view could only display a maximum of 100 nodes. If you attempted to view more than 100 nodes, the web console would output a `Loading is taking longer than expected.` error message. With this release, the `MAX_NODES_LIMIT` parameter for the web console is set to `200` so that the web console can display a maximum of 200 nodes. (link:https://issues.redhat.com/browse/OCPBUGS-32340[*OCPBUGS-32340*]
      Show
      * Previously, the {product-title} web console *Topology* view could only display a maximum of 100 nodes. If you attempted to view more than 100 nodes, the web console would output a `Loading is taking longer than expected.` error message. With this release, the `MAX_NODES_LIMIT` parameter for the web console is set to `200` so that the web console can display a maximum of 200 nodes. (link: https://issues.redhat.com/browse/OCPBUGS-32340 [* OCPBUGS-32340 *]
    • Enhancement
    • Done

      Description of problem:

          Increase MAX_NODES_LIMIT to 300 for 4.16 and 200 for 4.15 so that users don't see alert "Loading is taking longer than expected" in topology page

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

          4.15

      How reproducible:

          Always

      Steps to Reproduce:

          1. Create more than 100 nodes in a namespace
          

      Additional info:

          

              rh-ee-lprabhu Lokananda Prabhu
              rh-ee-lprabhu Lokananda Prabhu
              Sanket Pathak Sanket Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: