kubernetes-nmstate interprets interface names as float64 and subsequently crashes in OCP 4
Issue
- After deploying CNFs in our OpenShift 4.8.24 we still face the problem that interface names are understood as float64 and not strings
- Using Kubernetes-nmstate Operator configuration on an application, two interfaces were interpreted as float64 in two different namespaces
-
Error in kubernetes
nmstate-handler
Pod logs:E0209 19:33:22.394992 1 runtime.go:78] Observed a panic: &runtime.TypeAssertionError{_interface:(*runtime._type)(0x14ca120), concrete:(*runtime._type)(0x1460040), asserted: (*runtime._type). (0x1483a00), missingMethod:""} (interface conversion: interface {} is float64, not string) goroutine 310 [running]: k8s.io/apimachinery/pkg/util/runtime.logPanic(0x15050c0, 0xc00010af90) /go/src/github.com/nmstate/kubernetes-nmstate/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:74 +0xa3 k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
Environment
- Red Hat OpenShift Container Platform (RHOCP)
o 4.10
o 4.9
o 4.8 - Kubernetes-nmstate Operator
- Container Native Virtualization (CNV)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.