+++ This bug was initially created as a clone of Bug #1872336 +++ Description of problem: When I use a Pipeline Trigger and I test it out with Postman, it tried to create a PipelineRun with the same name everytime, resulting in an error. Version-Release number of selected component (if applicable): Pipelines Operator v1.0.1, OpenShift 4.5.0-rc.4 How reproducible: Always Steps to Reproduce: 1. Installed the Operator 2. Created a sample task. I replaced the $(input.params.appName) by a string to output hello world and removed the parameter appname 3. Created a pipeline with this task alone 4. Added a trigger using the "Add Trigger" option 5. Used the following payload in Postman (see request.json). The Payload is the payload created by Github to which I added a "name" property. 6. Did a POST request to the event listener URL 7. A PipelineRun was created and the pipeline ran 8. Tried the same request again 9. Got the following error message (see error.json) Actual results: Got an error message about the pipeline run already existing, the pipeline was not executed again. Expected results: The pipelinerun should have a unique id and should start the pipeline Additional info: None --- Additional comment from cjerolim on 2020-08-25 14:07:38 UTC --- Jira Issue: https://issues.redhat.com/browse/ODC-4236 GitHub PR: https://github.com/openshift/console/pull/6248
Created attachment 1721624 [details] PipelineRun created by Trigger have a unique id
Verified on build version: 4.5.0-0.ci-2020-10-09-095838 Browser version: chrome 84
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.5.15 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4228