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

Topology screen crashes when completed pod is selected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Major Major
    • None
    • 4.15.z
    • Dev Console
    • Important
    • None
    • ODC Sprint 3261, ODC Sprint 3262
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, when cronjobs were created, the creation of pods happens very quickly, causing the component that is constantly fetching new pods off the cronjob to fail. With this update, a 3 second delay was added before starting to fetch the pods of the cronjob. (link:https://issues.redhat.com/browse/OCPBUGS-37584[(*OCPBUGS-37584*)])
      Show
      * Previously, when cronjobs were created, the creation of pods happens very quickly, causing the component that is constantly fetching new pods off the cronjob to fail. With this update, a 3 second delay was added before starting to fetch the pods of the cronjob. (link: https://issues.redhat.com/browse/OCPBUGS-37584 [(* OCPBUGS-37584 *)])
    • Bug Fix
    • Done

      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:

            [OCPBUGS-37584] Topology screen crashes when completed pod is selected

            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 (Important: OpenShift Container Platform 4.18.1 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:6122

            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 (Important: OpenShift Container Platform 4.18.1 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:6122

            Avik Kundu added a comment -

            Verified on 4.18.0-0.nightly-2024-09-13-024933

            Avik Kundu added a comment - Verified on 4.18.0-0.nightly-2024-09-13-024933

            OpenShift Jira Bot added a comment -

            Hi avik6028,

            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 avik6028 , 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.

              avik6028 Avik Kundu
              rhn-support-dgautam Dhruv Gautam
              Sanket Pathak Sanket Pathak
              Votes:
              3 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: