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

Topology screen crashes when completed pod is selected

XMLWordPrintable

    • Important
    • None
    • ODC Sprint 3263, ODC Sprint 3264
    • 2
    • False
    • Hide

      None

      Show
      None
    • Hide
      Cause: When cron jobs are created, the creation of pods happens very quickly, crashing the component that is constantly fetching new pods of the cron job.
      Consequence: The Topology page crashes
      Fix: A 3 second delay was added before starting to fetch the pods of the cronjob.
      Result: Bug doesn't present anymore.
      Show
      Cause: When cron jobs are created, the creation of pods happens very quickly, crashing the component that is constantly fetching new pods of the cron job. Consequence: The Topology page crashes Fix: A 3 second delay was added before starting to fetch the pods of the cronjob. Result: Bug doesn't present anymore.
    • Bug Fix
    • In Progress

      This is a clone of issue OCPBUGS-42015. The following is the description of the original issue:


      Description of problem:

      Topology screen crashes and reports "Oh no! something went wrong" when a pod in completed state is selected.

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

      RHOCP 4.15.18    

      How reproducible:

      100%

      Steps to Reproduce:

      1. Switch to developer mode
      2. Select Topology
      3. Select a project that has completed cron jobs like openshift-image-registry
      4. Click the green CronJob Object
      5. Observe Crash

      Actual results:

      The Topology screen crashes with error "Oh no! Something went wrong."

      Expected results:

      After clicking the completed pod / workload, the screen should display the information related to it.

      Additional info:

          

            avik6028 Avik Kundu
            rhn-support-dahernan David Hernandez Fernandez
            Sanket Pathak Sanket Pathak
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: