Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-7032

Pipelines web console cannot properly display cluster resolver Tasks in Pipeline Builder

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • Pipelines 1.16.0
    • UI
    • None
    • 1
    • False
    • None
    • False
    • ODC Sprint 3270

      Description of problem:

      OCP Pipelines' console plugin is not able to resolve Tasks in a Pipeline when using the standard cluster resolver. Each task is resolved as "custom" instead, resulting in the inability to use the Pipeline Builder to add Tasks or modify their parameters, as well as a warning on the Task indicating the "Task does not exist".

      This does not affect the cluster's ability to run the pipelines, which is fine, as the tasks are resolved correctly. Only the web view is impacted and unable to pull the proper spec.

      Workaround: Using the ClusterTasks allows the Task to be modifiable in the Pipeline Builder, but ClusterTasks have been deprecated since 1.10, and are fully removed and unavailable in 1.17.

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

      • OpenShift Pipelines 1.16, 1.17
      • Supported version of OpenShift (tested on 4.16.10)

      Steps to Reproduce

      1. Install Pipelines 1.16
      2. Create Pipeline with following manifest:
      apiVersion: tekton.dev/v1
      kind: Pipeline
      metadata:
        name: new-pipeline
      spec:
        tasks:
          - name: git-clone
            params:
              - name: URL
                value: 'https://github.com/github/gitignore'  # Any barebones public git project will work here
            taskRef:
              params:
                - name: kind
                  value: task
                - name: name
                  value: git-clone
                - name: namespace
                  value: openshift-pipelines
              resolver: cluster
            workspaces:
              - name: output
                workspace: source
        workspaces:
          - name: source
            optional: false
        params: []
        finally: []
      
      1. In web console, in Pipelines dashboard, click Edit Pipeline to view Pipeline Builder
         

        Actual results:

      Pipeline shows red exclamation point indicating warning, alternate text reads "Task does not exist". Task cannot be clicked to modify parameters.

      Modifying pipeline yaml to use ClusterTask instead via

      kind: ClusterTask
      name: git-clone
      

      shows parameters properly for tasks.

      Expected results:

      Pipeline shows Tasks without warning. Clicking Task shows parameters screen for modification.

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Acceptance criteria: 

      Pipeline builder does not show warning for Tasks available via cluster resolver.

            [SRVKP-7032] Pipelines web console cannot properly display cluster resolver Tasks in Pipeline Builder

            Lokananda Prabhu moved the issue to Closed, but:

            • the issue has one or more violating labels (docs-pending, release-notes-pending, tests-pending)
            • the issue cannot be marked for review or cannot be closed without release notes, documentation and tests
            • remove relevant labels after careful consideration and update the status again

            OpenShift Jira Bot added a comment - Lokananda Prabhu moved the issue to Closed, but: the issue has one or more violating labels ( docs-pending , release-notes-pending , tests-pending ) the issue cannot be marked for review or cannot be closed without release notes, documentation and tests remove relevant labels after careful consideration and update the status again

              rh-ee-lprabhu Lokananda Prabhu
              rhn-support-jorbell Jordan Bell
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: