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

Pipeline selector in the Run creation form does not show the correct list based on the selected project

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • RHODS_1.28.0_GA
    • RHODS_1.27.0_GA
    • UI
    • False
    • None
    • False
    • Testable
    • No
    • 1.28.0
    • No
    • Hide
      == Changing the host project when creating a pipeline ran results in an inaccurate list of available pipelines
      If you changed the host project while creating a pipeline run, the interface failed to make the pipelines of the new host project available. Instead, the interface showed pipelines that belong to the project you initially selected on the *Data Science Pipelines* -> *Runs* page. This issue is now fixed. You no longer select a pipeline from the *Create run* page. The pipeline selection is automatically updated when you click the *Create run* button, based on the current project and its pipeline.
      Show
      == Changing the host project when creating a pipeline ran results in an inaccurate list of available pipelines If you changed the host project while creating a pipeline run, the interface failed to make the pipelines of the new host project available. Instead, the interface showed pipelines that belong to the project you initially selected on the *Data Science Pipelines* -> *Runs* page. This issue is now fixed. You no longer select a pipeline from the *Create run* page. The pipeline selection is automatically updated when you click the *Create run* button, based on the current project and its pipeline.
    • Bug Fix
    • Done
    • No
    • Pending
    • None
    • RHODS 1.28

    Description

      Description of problem:

      When the user changes the target project while creating a pipeline run, the dropdown containing the pipeline names does not load the pipelines of the new selected project. It keeps showing the pipelines created in the project that was selected in the "Pipeline Runs" home page.

      The below GIF shows the issue: 

      • the two projects have 1 pipeline each with different names "my-iris" vs "second-iris"
      • when creating the run, the pipeline selector is always showing "second iris" even if i select the other project

      GIF:

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

      Steps to Reproduce

      1. create 2 DS projects from Dashboard UI
      2. create a pipeline server for each DS Project
      3. create a pipeline for each DS project (ensure to use different names)
      4. go to "Data Science Pipelines > Runs"
      5. select project A
      6. click "Create run"
      7. click "Select pipeiine" dropdown
      8. select project B from the dropdown at the top of the form
      9. click "Select pipeiine" dropdown

      You can repeat the process inverting project A with project B in the steps from 5 to 9

      Actual results:

      step 7) and 9) always shows the pipeline contained in project A, regardless the selector

      Expected results:

      TBD

      Possibilities:

      • In the "Create run" form user can see the available pipeline in the selected project
      • "Create run" page does not have the project selector. It assumes you have selected the desired project in the "Run" home page (step 5)

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      RHODS v1.27.0

      Workaround:

      Additional info:

      if user goes ahead with the creation of the pipeline run having selected the wrong project name, the run is created in the project where the selected pipelines belongs.

      Attachments

        Activity

          People

            gkrumbac Gage Krumbach
            rhn-support-bdattoma Berto D'Attoma
            Berto D'Attoma Berto D'Attoma
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: