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

Developer Topology always blanks with large contents when first rendering

    XMLWordPrintable

Details

    • Important
    • ODC Sprint 228
    • 1
    • Rejected
    • False
    • Hide

      not a release blocker for 4.12

      Show
      not a release blocker for 4.12
    • Hide
      * Previously, when returning to the *Topology* view after moving all the elements out of the viewport, the initial state was restored and the *Topology* looks broken. With this fix, any node shown in the viewport is detected automatically. (link:https://issues.redhat.com/browse/OCPBUGS-2500[*OCPBUGS-2500*])
      Show
      * Previously, when returning to the *Topology* view after moving all the elements out of the viewport, the initial state was restored and the *Topology* looks broken. With this fix, any node shown in the viewport is detected automatically. (link: https://issues.redhat.com/browse/OCPBUGS-2500 [* OCPBUGS-2500 *])
    • Bug Fix
    • Done

    Description

      Description of problem:

      When the Ux switches to the Dev console the topology is always blank in a Project that has a large number of components.

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

       

      How reproducible:

      Always occurs

      Steps to Reproduce:

      1.Create a project with at least 12 components (Apps, Operators, knative Brokers)
2. Go to the Administrator Viewpoint
3. Switch to Developer Viewpoint/Topology
4. No components displayed
5. Click on 'fit to screen'
6. All components appear

      Actual results:

      Topology renders with all controls but no components visible (see screenshot 1)

      Expected results:

      All components should be visible

      Additional info:

       

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-4897 Developer Topology always blanks with large contents when first rendering

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-4897 Developer Topology always blanks with large contents when first rendering

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-2055 Developer Topology pages places new components incorrectly

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          links to

          GitHub openshift/console#12260: OCPBUGS-2500: Pan nodes into view if all nodes are not visible on load

          Activity

            People

              jephilli@redhat.com Jeffrey Phillips
              utherp0 Ian Lawson
              Sanket Pathak Sanket Pathak
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: