Bug 1869500

Summary: No serverless-operator bundle image in brew for OCP 4.6
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: OLMAssignee: Evan Cordell <ecordell>
OLM sub component: OLM QA Contact: Jian Zhang <jiazha>
Status: CLOSED NOTABUG Docs Contact:
Severity: low    
Priority: low CC: aos-bugs, bluddy, eparis, jokerman, krizza, yapei
Version: 4.6   
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: Environment:
Last Closed: 2020-09-09 20:14:11 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 Yadan Pei 2020-08-18 06:43:55 UTC 
Description of problem:
serverless-operator packagemanifests is not available in Red Hat Operators by default, also we can't find the bundle image for serverless-operator in brew

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-08-17-212631

How reproducible:
Always

Steps to Reproduce:
1. check packagemanifests
# oc get packagemanifests | grep serverless    
2. search in brew
https://brewweb.engineering.redhat.com/brew/search?terms=serverless-operator&type=package&match=regexp


Actual results:
1. # oc get packagemanifests | grep serverless 
nothing returned
2. no search results found. 

Expected results:
1-2. serverless-operator should be ready in brew and QE can mirror to continue our testing

Additional info:
in previous version of OCP, we can see
# oc get packagemanifests | grep serverless
serverless-operator                          Red Hat Operators     3h34m
Comment 3 Ben Luddy 2020-08-21 21:58:11 UTC 
This is expected due to the deprecation of appregistry-based operator catalogs beginning with OpenShift 4.6. The team that maintains the operator in question must complete a migration process to ensure that it is available by default in 4.6 clusters.

Due to the volume of questions, my team is assembling a FAQ to explain what is happening and help direct further questions.
Comment 4 Yadan Pei 2020-08-24 01:57:47 UTC 
Thanks for the details