Bug 1901871

Summary: catalog-operator repeatedly crashes with "runtime error: index out of range [0] with length 0"
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: OLMAssignee: Nick Hale <nhale>
OLM sub component: OperatorHub QA Contact: Jian Zhang <jiazha>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: dsover, jnordell, krizza, nhale, wking
Version: 4.6Keywords: ServiceDeliveryImpact
Target Milestone: ---   
Target Release: 4.6.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-21 13:23:59 UTC Type: ---
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: 1899835    
Bug Blocks:    

Comment 3 Jian Zhang 2020-12-14 05:54:43 UTC 
Cluster version is 4.6.0-0.nightly-2020-12-14-015205
[root@preserve-olm-env data]# oc -n openshift-operator-lifecycle-manager exec catalog-operator-6bc7d9ff89-rnszx -- olm --version
OLM version: 0.16.1
git commit: fe32277830b3dc086e014c0e3391de671e5f49f4

LGTM, verify it. The catalog-operator works well, no crash found.

[root@preserve-olm-env data]# oc get pods -n openshift-operator-lifecycle-manager 
NAME                                READY   STATUS    RESTARTS   AGE
catalog-operator-6bc7d9ff89-rnszx   1/1     Running   0          3h34m
olm-operator-748968646f-tqk76       1/1     Running   0          3h34m
packageserver-6cf594f9fc-8ml89      1/1     Running   0          3h28m
packageserver-6cf594f9fc-9rx8n      1/1     Running   0          3h28m
Comment 6 errata-xmlrpc 2020-12-21 13:23:59 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 (Important: OpenShift Container Platform 4.6.9 security and bug fix update), 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/RHSA-2020:5614