RHACS Central pod stuck in CrashLoopBackOff reports Invalid Memory Address or nil pointer dereference
Issue
The Central pod is in the CrashLoopBackOff state with logs as mentioned below
cve/fetcher: 2022/10/20 09:25:47.265749 orchestrator.go:237: Info: Successfully fetched 0 Kubernetes CVEs
cve/fetcher: 2022/10/20 09:25:47.265832 orchestrator.go:70: Error: failed to reconcile orchestrator OpenShift CVEs: no orchestrator scanners are integrated
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x33d357d]
goroutine 31 [running]:
...
Environment
- Red Hat OpenShift Container Platform (RHOCP)
- 4
- Red Hat Advance Cluster Security (RHACS)
- 3.72 and below
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
