-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18.z
-
None
-
None
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
The catalog-operator Pod crashed during Single Node OpenShift (SNO) cluster install, seemingly due to the bundles for the operators failing. Rather than continuing and entering the "bundle unpacking" error in the operators' Subscriptions, the catalog-operator Pod crashed instead:
---
time="2026-02-11T15:44:22Z" level=info msg="unpacking bundles" id=h6EhF namespace=metallb-system
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0x1f94bf0]
goroutine 528 [running]:
github.com/operator-framework/operator-lifecycle-manager/pkg/controller/bundle.sortUnpackJobs.func1(0xc005573ef0?, 0x0)
/build/vendor/github.com/operator-framework/operator-lifecycle-manager/pkg/controller/bundle/bundle_unpacker.go:889 +0x1f0
sort.insertionSort_func({0xc0059b3090?, 0xc004d39a80?}, 0x0, 0x5)
Version-Release number of selected component (if applicable):
4.18.24
How reproducible:
Inconsistent, appears to require some variation of the Jobs failing
Steps to Reproduce:
1. Install 4.18.24 SNO cluster
2. Attempt to install multiple operators
3. Have the bundles of some operators fail
Actual results:
catalog-operator Pod crashes
Expected results:
catalog-operator Pod continues, labeling each Subscription as having an issue with their bundles
Additional info:
- Issue appears to be similar but separate to
OCPBUGS-34173 - Issue is still resolved using the solution for the bundle unpacking error
