1860783 – [vsphere][upi] Got `Observed a panic: "invalid memory address or nil pointer dereference"` in MCO pod

Bug 1860783 - [vsphere][upi] Got `Observed a panic: "invalid memory address or nil pointer dereference"` in MCO pod

Summary: [vsphere][upi] Got `Observed a panic: "invalid memory address or nil pointer ...

Keywords:
Status:	CLOSED DUPLICATE of bug 1859230
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Machine Config Operator
Sub Component:
Version:	4.6
Hardware:	Unspecified
OS:	Unspecified
Priority:	high
Severity:	high
Target Milestone:	---
Target Release:	4.6.0
Assignee:	Kirsten Garrison
QA Contact:	Michael Nguyen
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2020-07-27 07:00 UTC by jima
Modified:	2020-07-27 08:26 UTC (History)
CC List:	1 user (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2020-07-27 08:26:24 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description jima 2020-07-27 07:00:02 UTC

Description of problem:
Install ocp upi on vsphere with nightly build:4.6.0-0.nightly-2020-07-25-091217.
When waiting for worker node pending CSR and approve them, but failed.
From worker vm console, could not get ignition file.
Then check mco pod, error is shown in pod's log:
$ oc logs pod/machine-config-operator-7879f6dc78-fp7x7 -n openshift-machine-config-operator
I0727 03:08:22.091332       1 start.go:46] Version: 4.6.0-0.nightly-2020-07-25-091217 (Raw: v4.6.0-202007250017.p0-dirty, Hash: ab2673986646c62bc6599931d22f050ffd5871db)
I0727 03:08:22.093597       1 leaderelection.go:242] attempting to acquire leader lease  openshift-machine-config-operator/machine-config...
I0727 03:10:19.904385       1 leaderelection.go:252] successfully acquired lease openshift-machine-config-operator/machine-config
I0727 03:10:20.225201       1 operator.go:270] Starting MachineConfigOperator
E0727 03:10:20.248072       1 runtime.go:78] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
goroutine 247 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic(0x1814240, 0x2a35120)
    /go/src/github.com/openshift/machine-config-operator/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:74 +0xa3
k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
    /go/src/github.com/openshift/machine-config-operator/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:48 +0x82
panic(0x1814240, 0x2a35120)
    /opt/rh/go-toolset-1.14/root/usr/lib/go-toolset-1.14-golang/src/runtime/panic.go:969 +0x166
github.com/openshift/machine-config-operator/pkg/operator.getIgnitionHost(0xc0002d8368, 0xc000a88420, 0x1a41f59, 0x18, 0xc0003680c8)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/sync.go:336 +0x319
github.com/openshift/machine-config-operator/pkg/operator.(*Operator).syncRenderConfig(0xc0004c7200, 0x0, 0xc00e0c2dfe, 0x23eb713ab67)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/sync.go:300 +0x10c7
github.com/openshift/machine-config-operator/pkg/operator.(*Operator).syncAll(0xc0004c7200, 0xc000707ca8, 0x6, 0x6, 0xc0005fcc01, 0x413893)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/sync.go:69 +0x177
github.com/openshift/machine-config-operator/pkg/operator.(*Operator).sync(0xc0004c7200, 0xc0001f0960, 0x30, 0x0, 0x0)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/operator.go:362 +0x40a
github.com/openshift/machine-config-operator/pkg/operator.(*Operator).processNextWorkItem(0xc0004c7200, 0x203000)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/operator.go:318 +0xd2
github.com/openshift/machine-config-operator/pkg/operator.(*Operator).worker(0xc0004c7200)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/operator.go:307 +0x2b
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0xc0008776f0)
    /go/src/github.com/openshift/machine-config-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:155 +0x5f
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc0008776f0, 0x1cbf1c0, 0xc0001cd2c0, 0xc00000e601, 0xc000188180)
    /go/src/github.com/openshift/machine-config-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:156 +0xa3
k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc0008776f0, 0x3b9aca00, 0x0, 0x1, 0xc000188180)
    /go/src/github.com/openshift/machine-config-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 +0xe2
k8s.io/apimachinery/pkg/util/wait.Until(0xc0008776f0, 0x3b9aca00, 0xc000188180)
    /go/src/github.com/openshift/machine-config-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:90 +0x4d
created by github.com/openshift/machine-config-operator/pkg/operator.(*Operator).Run
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/operator.go:276 +0x3dc
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
    panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x168aea9]

goroutine 247 [running]:
k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
    /go/src/github.com/openshift/machine-config-operator/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:55 +0x105
panic(0x1814240, 0x2a35120)
    /opt/rh/go-toolset-1.14/root/usr/lib/go-toolset-1.14-golang/src/runtime/panic.go:969 +0x166
github.com/openshift/machine-config-operator/pkg/operator.getIgnitionHost(0xc0002d8368, 0xc000a88420, 0x1a41f59, 0x18, 0xc0003680c8)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/sync.go:336 +0x319
github.com/openshift/machine-config-operator/pkg/operator.(*Operator).syncRenderConfig(0xc0004c7200, 0x0, 0xc00e0c2dfe, 0x23eb713ab67)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/sync.go:300 +0x10c7
github.com/openshift/machine-config-operator/pkg/operator.(*Operator).syncAll(0xc0004c7200, 0xc000707ca8, 0x6, 0x6, 0xc0005fcc01, 0x413893)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/sync.go:69 +0x177
github.com/openshift/machine-config-operator/pkg/operator.(*Operator).sync(0xc0004c7200, 0xc0001f0960, 0x30, 0x0, 0x0)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/operator.go:362 +0x40a
github.com/openshift/machine-config-operator/pkg/operator.(*Operator).processNextWorkItem(0xc0004c7200, 0x203000)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/operator.go:318 +0xd2
github.com/openshift/machine-config-operator/pkg/operator.(*Operator).worker(0xc0004c7200)
    /go/src/github.com/openshift/machine-config-operator/pkg/operator/operator.go:307 +0x2b
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1(0xc0008776f0)
    /go/src/github.com/openshift/machine-config-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:155 +0x5f
k8s.io/apimachinery/pkg/util/wait.BackoffUntil(0xc0008776f0, 0x1cbf1c0, 0xc0001cd2c0, 0xc00000e601, 0xc000188180)
    /go/src/github.com/openshift/machine-config-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:156 +0xa3
k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc0008776f0, 0x3b9aca00, 0x0, 0x1, 0xc000188180)
    /go/src/github.com/openshift/machine-config-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 +0xe2
k8s.io/apimachinery/pkg/util/wait.Until(0xc0008776f0, 0x3b9aca00, 0xc000188180)
    /go/src/github.com/openshift/machine-config-operator/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:90 +0x4d
created by github.com/openshift/machine-config-operator/pkg/operator.(*Operator).Run


Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-07-25-091217

How reproducible:
Always

Steps to Reproduce:
1.Install cluster with 4.6.0-0.nightly-2020-07-25-091217
2.Waiting for approving pending csr and timeout
3.

Actual results:
Compute node could not be provisioned

Expected results:
Installation is successful

Additional info:

Comment 2 Antonio Murdaca 2020-07-27 08:26:24 UTC


*** This bug has been marked as a duplicate of bug 1859230 ***

Note You need to log in before you can comment on or make changes to this bug.