Bug 1805948

Summary:	Pipeline: Start last run starts a pipeline from different namespace
Product:	OpenShift Container Platform	Reporter:	cvogt
Component:	Dev Console	Assignee:	cvogt
Status:	CLOSED ERRATA	QA Contact:	Gajanan More <gamore>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4	CC:	aos-bugs, nmukherj, rgarg
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1805945	Environment:	Version: 4.4.0-0.ci-2020-02-20-044240 Cluster ID: 223e19ec-0f8c-499c-9e99-dcb9fa4ed59f Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.116 Safari/537.36
Last Closed:	2020-05-13 21:59:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1805945
Bug Blocks:

Description cvogt 2020-02-21 18:01:34 UTC

+++ This bug was initially created as a clone of Bug #1805945 +++

Description of problem:
Pipeline run gets created in wrong namespace because the `Start Last Run` action should not be present.

How reproducible:


Steps to Reproduce:
1. install OpenShift Pipelines and follow steps in https://github.com/openshift/pipelines-tutorial/ twice in two different namespaces, don't create the second pipeline run
2. open Pipeline -> Pipeline Runs in console
3. open Actions dropdown
4. select Start Last Run


Actual results:
pipelinerun is created in a different namespace

Expected results:
there is no Start Last Run option because it's the first time the pipeline is started

Comment 3 Ruchir Garg 2020-03-02 06:38:32 UTC

Bulk assigning all to Gajanan for verification.

Comment 4 Gajanan More 2020-03-03 12:24:16 UTC

Verified on build : 4.4.0-0.ci-2020-03-01-110146
Chrome browser: 76.0.3809.132 

Validated by Sanket Pathak (ODC-3109)

Comment 6 errata-xmlrpc 2020-05-13 21:59:46 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, 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:0581