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

Increase Max node limit for topology page to 300

XMLWordPrintable

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

      None

      Show
      None
    • Hide
      * Previously, the maximum number of nodes was set to 100 on the *topology* page. A persistant alert, "Loading is taking longer than expected." was provided. With this update, the limit of nodes is increased to 300. (link:https://issues.redhat.com/browse/OCPBUGS-32307[*OCPBUGS-32307*])
      Show
      * Previously, the maximum number of nodes was set to 100 on the *topology* page. A persistant alert, "Loading is taking longer than expected." was provided. With this update, the limit of nodes is increased to 300. (link: https://issues.redhat.com/browse/OCPBUGS-32307 [* OCPBUGS-32307 *])
    • Enhancement
    • In Progress

      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:

            [OCPBUGS-32307] Increase Max node limit for topology page to 300

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (Critical: OpenShift Container Platform 4.16.0 bug fix and security update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHSA-2024:0041

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (Critical: OpenShift Container Platform 4.16.0 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2024:0041

            Christoph Jerolimov added a comment -

            Verified on 4.16.0-0.ci-2024-04-19-160249

            Christoph Jerolimov added a comment - Verified on 4.16.0-0.ci-2024-04-19-160249

            OpenShift Jira Bot added a comment -

            Hi rh-ee-lprabhu,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi rh-ee-lprabhu , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

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

                Created:
                Updated:
                Resolved: