Bug 1878849 - PipelineRun created by Trigger should have a unique id
Summary: PipelineRun created by Trigger should have a unique id
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.5.z
Assignee: Christoph Jerolimov
QA Contact: spathak@redhat.com
URL:
Whiteboard:
Depends On: 1872336
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-14 16:36 UTC by OpenShift BugZilla Robot
Modified: 2020-10-19 14:54 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-19 14:54:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
PipelineRun created by Trigger have a unique id (1.53 MB, video/webm)
2020-10-14 21:49 UTC, spathak@redhat.com
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 6615 0 None closed Bug 1878849: Use metadata.generatorName when create a pipeline trigger 2020-12-22 20:13:29 UTC
Red Hat Product Errata RHBA-2020:4228 0 None None None 2020-10-19 14:54:48 UTC

Description OpenShift BugZilla Robot 2020-09-14 16:36:31 UTC
+++ 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

Comment 3 spathak@redhat.com 2020-10-14 21:49:27 UTC
Created attachment 1721624 [details]
PipelineRun created by Trigger have a unique id

Comment 4 spathak@redhat.com 2020-10-14 21:51:00 UTC
Verified on build version: 4.5.0-0.ci-2020-10-09-095838
Browser version: chrome 84

Comment 6 errata-xmlrpc 2020-10-19 14:54:26 UTC
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


Note You need to log in before you can comment on or make changes to this bug.