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

Workbench UI dialog "Starting server" does not refresh

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • RHODS_1.31.0_GA
    • UI, Workbenches
    • None
    • False
    • None
    • False
    • Testable
    • No
    • No
    • No
    • Pending
    • None
    • Medium

      Description of problem:

      Creating workbench in a new DS project, has an option to see progress under "Status" column with a link "Starting..."

      However, the dialog opened does not get updated and keep displaying:

      Starting server
      
      Depending on the size and resources requested, this can take several minutes.
      
      Waiting for server request to start...0%

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

      RHODS 1.31

      Steps to Reproduce

      1. Login with a simple user (non admin) to DS dashboard
      2. Create a new Workbench (e.g. with Trusty AI)
      3. Click on "starting" label
      4. Click on the "event log" link
      5. Wait until workbech is ready
      6. Click "Open" button

      Actual results:

       

       

      Note that the actual status of the workbench according to OCP namespace is Running:

       

      Expected results:

      The Dialog should be automatically refreshed to display "Running" status and a button "Open" should replace the "Cancel" button.

      Pressing on the open button should launch the workbench in a new browser tab.

      Reproducibility (Always/Intermittent/Only Once):

      Build Details:

      Workaround:

      Pressing Browser refresh button (F5) changes the status to "Running"

      Additional info:

              Unassigned Unassigned
              nmanos@redhat.com Noam Manos
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: