Description of Problem

• The Applications page of the GitOps Console Plugin does not render because of an unhandled JS error

Additional Info

• TypeError: Cannot read properties of undefined (reading '0')
      at https://console-openshift-console.apps.rosa.bu-hub.rhxm.p3.openshiftapps.com/api/plugins/gitops-plugin/exposed-ApplicationList-chunk-45676dfc517c2e1067a4.min.js:1:7349
      at Array.forEach (<anonymous>)
      at https://console-openshift-console.apps.rosa.bu-hub.rhxm.p3.openshiftapps.com/api/plugins/gitops-plugin/exposed-ApplicationList-chunk-45676dfc517c2e1067a4.min.js:1:6177
      at C (https://console-openshift-console.apps.rosa.bu-hub.rhxm.p3.openshiftapps.com/api/plugins/gitops-plugin/exposed-ApplicationList-chunk-45676dfc517c2e1067a4.min.js:1:7775)
      at so (https://console-openshift-console.apps.rosa.bu-hub.rhxm.p3.openshiftapps.com/static/vendors~main-chunk-93837-51729aab8176600c09a5.min.js:52:2867160)
      at Vo (https://console-openshift-console.apps.rosa.bu-hub.rhxm.p3.openshiftapps.com/static/vendors~main-chunk-93837-51729aab8176600c09a5.min.js:52:2876658)
      at $a (https://console-openshift-console.apps.rosa.bu-hub.rhxm.p3.openshiftapps.com/static/vendors~main-chunk-93837-51729aab8176600c09a5.min.js:52:2919981)
      at Il (https://console-openshift-console.apps.rosa.bu-hub.rhxm.p3.openshiftapps.com/static/vendors~main-chunk-93837-51729aab8176600c09a5.min.js:52:2906355)
      at El (https://console-openshift-console.apps.rosa.bu-hub.rhxm.p3.openshiftapps.com/static/vendors~main-chunk-93837-51729aab8176600c09a5.min.js:52:2906283)
      at Sl (https://console-openshift-console.apps.rosa.bu-hub.rhxm.p3.openshiftapps.com/static/vendors~main-chunk-93837-51729aab8176600c09a5.min.js:52:2906146)

Problem Reproduction

• Go to:  /k8s/all-namespaces/argoproj.io~v1alpha1~Application
• Page does not load with error

Reproducibility

• Always

Prerequisites/Environment

• <OpenShift, managed service (e.g., ROSA, ARO), operators, layered product, and other software versions, build details>

Steps to Reproduce

• ...

Expected Results

• ...

Actual Results

• ...

Problem Analysis

• <Completed by engineering team as part of the triage/refinement process>

Root Cause

• <What is the root cause of the problem? Or, why is it not a bug?>

Workaround (If Possible)

• <Are there any workarounds we can provide to the customers?>

Fix Approaches

• <If we decide to fix this bug, how will we do it?>

Acceptance Criteria

• ...

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.