Refactor PipelineRun and Run yamls in conversion_test to avoid flake

[JeromeJu]

Changes

This commit refactors the yamls in the conversion test to aovid flake
where the TaskRun and the PipelineRun could run forever:

• remove the resources related codes
• change the workspace usage that are not present
• updates the params specifications

fixes: #6672
/kind misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• [n/a] Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• Has Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• [n/a] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• [n/a] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[dibyom]

This task looks simple enough that it should not take 5 mins to run.
Have we looked into why the task is timing out? Anything in the status/logs of the failing run or the controller logs?

[JeromeJu]

This task looks simple enough that it should not take 5 mins to run. Have we looked into why the task is timing out? Anything in the status/logs of the failing run or the controller logs?

I think from the build logs in the issue https://prow.tekton.dev/view/gs/tekton-prow/pr-logs/pull/tektoncd_pipeline/6663/pull-tekton-pipeline-alpha-integration-tests/1658558758315364352, it has been reconciled Succeeded and waited timeout:

    stream.go:305: I 20:02:20.740 tekton-pipelines-controller-66b8bdc479-g4zqb [github.com.tektoncd.pipeline.pkg.reconciler.taskrun.Reconciler] [arendelle-fqvtt/pipeline-run-c-r-d-conversion-wgsdqpcl-fetch-secure-data] Reconcile succeeded
    conversion_test.go:910: Failed waiting for v1 pipelineRun done: "pipeline-run-c-r-d-conversion-wgsdqpcl" failed

This seems to me that it has been timed out for waiting in 60s if I am not mistaken by the last part of the logs 🤔 .

[dibyom]

This seems to me that it has been timed out for waiting in 60s if I am not mistaken by the last part of the logs

Sure, that's a good start but we should look into why the pipeline is timing out waiting for 60s - the actual task only seems to echo hello so its really weird that it will take a entire minute to finish running.

Some other oddities I noticed in the pipeline is that we are referencing a workspace with a secret but that is never used (is the secret even present?). Also, some of the tasks/pipelines have references to pipeline resources - shouldn't they fail to get created?

[JeromeJu]

This seems to me that it has been timed out for waiting in 60s if I am not mistaken by the last part of the logs

Sure, that's a good start but we should look into why the pipeline is timing out waiting for 60s - the actual task only seems to echo hello so its really weird that it will take a entire minute to finish running.

Some other oddities I noticed in the pipeline is that we are referencing a workspace with a secret but that is never used (is the secret even present?). Also, some of the tasks/pipelines have references to pipeline resources - shouldn't they fail to get created?

Thanks @dibyom , I've updated the PR, I've mistaken that it could be longer than 60s while having the previous functionalities before we remove all the resources. I have validated the taskrun and pipelineruns yaml respectively.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dibyom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dibyom]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Yongxuanzhang]

/lgtm