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

PAC runs different version of task  than the one which is desired. 

    XMLWordPrintable

Details

    • 5
    • Pipelines Sprint 256, Pipelines Sprint 257, Pipelines Sprint 258, Pipelines Sprint 259, Pipelines Sprint 261 TekShift, Pipelines Sprint TekShift 262

    Description

      Description of problem:

      Client  is having issue with PAC - problem with task versions .
      They have  .tekton folder which has a few pipelines. Everything works correct if all same tasks in all pipelines are the same. The problem started if for example: one pipeline has task 0.1 and the other pipeline has 0.4.  Than PAC has a problem to run correct task and in some cases it run different version that defined (for example from other pipeline).

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

      OCP:4.13.9
      openshift-pipelines-operator-rh.v1.11

      Steps to Reproduce:
       
       Client have provided the  following details which provides better insights of the issue :
       
      1. pipelines-tasks-problem - the equivalent of our repo in which we keep Pipelines and tasks
      2. pac-tasks-problem - the equivalent of our repo with the application in which there is a folder .tekton from PipelineRun.

      Repositories are examples and do not have specific tasks.

      Their main purpose is to show how client hold tasks and pipelines and what exactly is the problem.
      Referring to previous messages, the main problem is taking the wrong versions of tasks. Client have presented it as follows. In the pac-tasks-problem repository, we have two pipelines in the tekton folder.
      If we see in line 20 we have a link to the task. In pipeline-1 the link is to task version 0.1 and in pipeline-2 link is to task version 0.3
      With this configuration, pac does not work properly and when trying to start pipeline-2 there are situations that the task in version 0.1 (from pipeline-2) is taken, and not as it is defined in version 0.3. 
      This problem does not arise if the same task in each pipeline is of the same version.

      Actual results:

      Client is not been able to run the task that they want because in some cases PAC runs different task 

      Expected results:

      Client should be able to run the task that they desire . 

       

      Attachments

        Activity

          People

            piyushgarg001 Piyush Garg
            rhn-support-dtambat Darshan Tambat
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: