Catalog operator pod crashes with panic invalid memory address or nil pointer dereference

Solution Verified - Updated -

Issue

  • The catalog-operator pod crashes unpacking bundles with the following error:

    level=debug msg="unpacking bundles" id=aYHGB namespace=openshift-storage
    panic: runtime error: invalid memory address or nil pointer dereference
    [signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x1d81a26]
    
  • The catalog-operator pod crashes during SNO cluster installation with errors like below in the pod logs.

    level=info msg="starting workers..."
    panic: runtime error: invalid memory address or nil pointer dereference
    [signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x1d761e6]
    
    goroutine 469 [running]:
    github.com/operator-framework/operator-lifecycle-manager/pkg/controller/bundle.sortUnpackJobs.func1(0xc002bdca20?, 0x0?)
         /build/vendor/github.com/operator-framework/operator-lifecycle-manager/pkg/controller/bundle/bundle_unpacker.go:844 +0xc6
    sort.insertionSort_func({0xc002b7cfb0?, 0xc0029fffe0?}, 0x0, 0x3)
         /usr/lib/golang/src/sort/zsortfunc.go:12 +0xb1
     sort.pdqsort_func({0xc002b7cfb0?, 0xc0029fffe0?}, 0x7f07987eab38?, 0x18?, 0xc001e80000?)
         /usr/lib/golang/src/sort/zsortfunc.go:73 +0x2dd
    
  • Solution for similar issue catalog operator pod crashing with panic: runtime error: invalid memory address or nil pointer dereference is not solving the error.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • OpenShift Operator Lifecycle Manager (OLM)
  • catalog-operator pod
  • Cluster upgrade
  • Single Node OpenShift (SNO)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content