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

Topology view shows wrong logo on items if multiple CRDs shared the same short name

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Low
    • No
    • None
    • None
    • Rejected
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      In a test cluster I have two CRDs which have the same short name in common: Notebook. One is from RHODS (RedHat OpenShift Data Science) operator and one is from Intel OpenVINO Toolkit operator.
      
      The issue is that when I create a Notebook CR from RHODS, if I go to Topology page of OCP Console, my notebook node is showing the Intel Openvino logo on top of it.

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

       

      How reproducible:

      Always

      Steps to Reproduce:

      1. Install Intel Openvino toolkit from OperatorHub
      2. Install RHODS operator from OperatorHub or OCM
      3. Create a RHODS workbench (i.e., Notebook CR) - user guide https://access.redhat.com/documentation/en-us/red_hat_openshift_data_science/1/html/working_on_data_science_projects/working-on-data-science-projects_nb-server#using_project_workbenches 
      4. go to OpenShift console > Topology
      
      I imagine this could be reproduced with any other operators sharing the same CRD name

      Actual results:

      RHODS Notebook CR node in the topology page has the Intel OpenVINO logo

      Expected results:

      RHODS Notebook CR node in the topology page does not have the Intel OpenVINO logo (classic OpenShift logo)

      Additional info:

       

              jakumar jaivardhan Kumar
              rhn-support-bdattoma Berto D'Attoma
              None
              None
              Sanket Pathak Sanket Pathak
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: