Bug 1761924

Summary:	[OLM][Auto] Error from server: no table handler registered for this type *operators.PackageManifestList
Product:	OpenShift Container Platform	Reporter:	Bruno Andrade <bandrade>
Component:	OLM	Assignee:	Alexander Greene <agreene>
OLM sub component:	OLM	QA Contact:	Bruno Andrade <bandrade>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	agreene, decarr, jiazha, mifiedle, scolange
Version:	4.3.0
Target Milestone:	---
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:	2020-01-23 11:07:31 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 Bruno Andrade 2019-10-15 15:16:58 UTC

Description of problem:

The following error happens when it is tried to obtain the 
packagemanifests from cluster:

oc get packagemanifest
Error from server: no table handler registered for this type *operators.PackageManifestList

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/23772/pull-ci-openshift-origin-master-e2e-aws/13098


Version-Release number of selected component (if applicable):
Cluster Version: 4.3.0-0.ci-2019-10-14-170839
OLM version: 0.12.0
git commit: 0c9e4bf058b96a522e46e167c575d24745a15894

How reproducible:
Always

Steps used to reproduce:
Mentioned in the description

Comment 1 Alexander Greene 2019-10-15 17:01:04 UTC

Moving to 4.3 as this is not release blocking for 4.2.  We will continue to try to reproduce there and backport any applicable fixes to z-stream releases.

Comment 2 Alexander Greene 2019-10-16 13:28:40 UTC

*** Bug 1761994 has been marked as a duplicate of this bug. ***

Comment 3 Alexander Greene 2019-10-16 13:34:35 UTC

*** Bug 1759690 has been marked as a duplicate of this bug. ***

Comment 5 Bruno Andrade 2019-10-23 21:37:18 UTC

Moving to VERIFIED, the package manifests are listed as expected.

Cluster Version:  4.3.0-0.nightly-2019-10-23-140012
OLM version: 0.12.0
git commit: fef533c6174413418a9dc581a54a6438f45da982


oc get packagemanifest
NAME                                         CATALOG               AGE
akka-cluster-operator-certified              Certified Operators   4h21m
anchore-engine                               Certified Operators   4h21m
appdynamics-operator                         Certified Operators   4h21m
appsody-operator-certified                   Certified Operators   4h21m
aqua-certified                               Certified Operators   4h21m
cic-operator                                 Certified Operators   4h21m
cockroachdb-certified                        Certified Operators   4h21m
couchbase-enterprise-certified               Certified Operators   4h21m
couchdb-operator-certified                   Certified Operators   4h21m
cpx-cic-operator                             Certified Operators   4h21m
crunchy-postgres-operator                    Certified Operators   4h21m
driverlessai-deployment-operator-certified   Certified Operators   4h21m
federatorai-certified                        Certified Operators   4h21m
hazelcast-enterprise-certified               Certified Operators   4h21m
insightedge-operator                         Certified Operators   4h21m
instana-agent                                Certified Operators   4h21m
joget-openshift-operator                     Certified Operators   4h21m
kong                                         Certified Operators   4h21m
kubeturbo-certified                          Certified Operators   4h21m
mariadb                                      Certified Operators   4h21m
memql-certified                              Certified Operators   4h21m

Comment 7 errata-xmlrpc 2020-01-23 11:07:31 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:0062