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

Bug 1877484

Summary:	newly released operators not showing up in operatorhub without forced marketplace sync
Product:	OpenShift Container Platform	Reporter:	lgallett
Component:	OLM	Assignee:	Anik <anbhatta>
OLM sub component:	OperatorHub	QA Contact:	Jian Zhang <jiazha>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	anbhatta, htariq
Version:	4.5
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1877564 (view as bug list)		Environment:
Last Closed:	2020-09-09 21:27:29 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:
Bug Depends On:
Bug Blocks:	1877564

Description lgallett 2020-09-09 17:51:04 UTC

Description of problem:

The hourly sync of the marketplace operator should re-download content from "redhat-operators" appregistry namespace. After waiting over a day certain operators are still not showing up in operatorhub despite their successful release to appregistry.

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


How reproducible:

unknown

Steps to Reproduce:
1. release a new operator (or equivalent)
2. wait an hour+
3. navigate to operatorhub UI

Actual results:

absence of the new release in operatorhub

Expected results:

presence of the new release in operatorhub


Additional info:

Comment 3 Haseeb Tariq 2020-09-09 21:27:29 UTC

Closing since operatorsource has been removed from 4.6. So not a bug in 4.6.
The fix will be targeted for 4.5.z in https://bugzilla.redhat.com/show_bug.cgi?id=1877564