Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-4308

"No Components Found" in RHODS Dashboad when rhods-enabled-applications-config is empty

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • RHODS_1.12.0_GA
    • UI
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

       

       

      Show
         
    • Yes
    • No
    • No
    • Yes
    • None
    • Low

      Description of problem:

      When going to RHODS Dashboard > Enabled and Explore sections, there are no applications shown and "No Components Found" message is shown. 

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. Go to RHODS Dashboard

      Actual results:

      Expected results:

      Reproducibility (Always/Intermittent/Only Once):

      The cluster had rhods v1.12.0-4 installed via script (non-addon flow). It was created yday (06/16/2022) and it was working just fine. After that it has been hibernated and resumed today.

      At the beginning, dashboard was apparently working fine, but I noticed that when installing ISVs (e.g., intel openvino or aikit), these were not showing up in the "Enabled" page. So, I restarted the dashboard pods (both killing them and scaling to 0). After the second restart (scaling down and up the deployment of dashboard) the error appeared.

      Build Details:

      RHODS v1.12.0-4

      Workaround:

      fix "rhods-enabled-applications-config" ConfigMap by adding 

       

      data:
         jupyterhub: 'true'

      Additional info:

       

      it happens because the "rhods-enabled-applications-config" ConfigMap was empty. Not sure how it got empty, jupyterhub should be always enabled

              Unassigned Unassigned
              rhn-support-bdattoma Berto D'Attoma
              Chris Chase
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: