CSI controller pods are in a CrashLoopBackOff with "failed to read config Error: 10:32: unknown escape sequence" on Red Hat Openshift Container Platform 4

Solution In Progress - Updated -

Issue

During installation of VSphere cluster Storage Operator is degraded with "csi-driver-controller" and "csi-driver-node" pods in CrashLoopBackOff state.

The error of the "csi-driver" container of the "csi-driver-controller" pod is the below:

"msg":"failed to run the driver. Err: +10:32: unknown escape sequence","TraceId":"d3b1889e-8f0f-4f8a-b34e-e6adc0258898","stacktrace":"sigs.k8s.io/vsphere-csi-driver/v3/pkg/csi/service.(*vsphereCSIDriver).Run\n\t/go/src/github.com/kubernetes-sigs/vsphere-csi-driver/pkg/csi/service/driver.go:203\nmain.main\n\t/go/src/github.com/kubernetes-sigs/vsphere-csi-driver/cmd/vsphere-csi/main.go:96\nruntime.main\n\t/usr/lib/golang/src/runtime/proc.go:271"}

Environment

Red Hat Openshift Container Platform (RHOCP) 4

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