Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1780471

Summary:	No proper image registry for 3rd-level operators to use when testing these operators on AWS, GCP, Azure and Vsphere.
Product:	OpenShift Container Platform	Reporter:	Qiaoling Tang <qitang>
Component:	Release	Assignee:	Luke Meyer <lmeyer>
Status:	CLOSED DUPLICATE	QA Contact:	Qiaoling Tang <qitang>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	4.3.0	CC:	anli, aos-bugs, chuo, jiazha, jokerman, lmeyer, scuppett, talessio
Target Milestone:	---	Keywords:	Reopened
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-12-17 14:13:00 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:

Comment 7 Anping Li 2019-12-17 02:32:56 UTC

That is not resolved. We are facing token conflict. we use token1 for openshift-release-dev. and token2 for openshift-qe-optional-operators. But we couldn't enable both of them as the global pull secrets.  I am trying to apply an account for QE department which can access both openshift-release-dev and  openshift-qe-optional-operators.

Comment 8 Stephen Cuppett 2019-12-17 14:13:00 UTC

This is a duplicate of 1773806 at this point. Will bring that back as a release blocker, etc..

*** This bug has been marked as a duplicate of bug 1773806 ***