Description of problem: Filtering the topology nodes by application, throws an error when the topology has operator backed services in the namespace. Version-Release number of selected component (if applicable): 4.4 How reproducible: Always Steps to reproduce: 1. Install an operator and create a CRD instance using dev catalog flow 2. Create an node from git flow 3. Use the application selector to filter the node by application Actual results: It breaks the UI Expected results: It should filter the nodes based on the application and should not break the UI Additional info:
Created attachment 1667741 [details] Topolgoy breaks when OBS nodes are in the canvas
Verified on 4.5 OpenShift Version 4.5.0-0.ci-2020-03-05-232742 Kubernetes Version v1.17.1 Channel stable-4.4 Cluster ID 0f33addf-9591-4d52-8e01-1b26e6ebd56a API Server https://api.gamore45installer0603.devcluster.openshift.com:6443
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.5 image release advisory), 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/RHBA-2020:2409