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

DS Pipelines UI missing node edges

    XMLWordPrintable

Details

    • False
    • None
    • False
    • Testable
    • No
    • 1.28.0
    • No
    • Hide
      == Data science pipeline graphs did not display node edges for running pipelines
      If you ran pipelines that did not contain Tekton-formatted `Parameters` or `when` expressions in their YAML code, the OpenShift Data Science user interface did not display connecting edges to and from graph nodes. For example, if you used a pipeline containing the `runAfter` property or `Workspaces`, the user interface displayed the graph for the executed pipeline without edge connections. The OpenShift Data Science user interface now displays connecting edges to and from graph nodes.
      Show
      == Data science pipeline graphs did not display node edges for running pipelines If you ran pipelines that did not contain Tekton-formatted `Parameters` or `when` expressions in their YAML code, the OpenShift Data Science user interface did not display connecting edges to and from graph nodes. For example, if you used a pipeline containing the `runAfter` property or `Workspaces`, the user interface displayed the graph for the executed pipeline without edge connections. The OpenShift Data Science user interface now displays connecting edges to and from graph nodes.
    • Bug Fix
    • Done
    • No
    • Pending
    • None
    • RHODS 1.28
    • Medium

    Description

      Description of problem:

       

      When running a DS Pipeline, the arrows seem to be missing.

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

      Steps to Reproduce

      1. upload included ds_example.yaml as a new pipeline
      2. run
      3. observe the run topology

      Actual results:

      Expected results:

      steps have arrows between them.

      Reproducibility (Always/Intermittent/Only Once):

      Build Details:

      Workaround:

      Use parameters in each node to refer to the node (heavy hack/workaround)

      Additional info:

      Attachments

        Issue Links

          is related to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. RHODS-5133 ML Pipelines capabilities in RHODS dashboard

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          mentioned on

          GitLab Merge request - Updated 2 upstream sources

          Activity

            People

              aballantyne Andrew Ballantyne
              cchase@redhat.com Chris Chase
              Jorge Garcia Oncins Jorge Garcia Oncins
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: