Bug 2073917

Summary:	Avoid using identical name for input and output imagestream
Product:	OpenShift Container Platform	Reporter:	Vinu K <vkochuku>
Component:	oc	Assignee:	Vinu K <vkochuku>
oc sub component:	oc	QA Contact:	zhou ying <yinzhou>
Status:	CLOSED DEFERRED	Docs Contact:
Severity:	low
Priority:	low	CC:	maszulik, mfojtik
Version:	4.11
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	CEE.neXT
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-09 01:17:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vinu K 2022-04-11 06:33:13 UTC

Description of problem: Avoid using identical name for input and output imagestream. The below build triggers itself when it finishes and continues in a loop.

$ oc new-build -D $'FROM registry.redhat.io/ubi8/ubi' --to=ubi:latest

Version-Release number of selected component (if applicable):
v4u11

How reproducible:


Steps to Reproduce:
1. Create a build
   $ oc new-build -D $'FROM registry.redhat.io/ubi8/ubi' --to=ubi:latest
2. It triggers itself when it finishes
3.

Actual results:
It does not throw any error.

Expected results:
It should give an error to use different build name.

Additional info:
https://github.com/openshift/oc/pull/1107

Comment 2 Shiftzilla 2023-03-09 01:17:13 UTC

OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.

https://issues.redhat.com/browse/OCPBUGS-9219