vmware-vsphere-csi-driver-operator goes in panic mode when the vcenter address is incorrect

  Vsphere IPI 4.17

    100%

$ oc logs vmware-vsphere-csi-driver-operator-74f65d4444-ljt78 -n openshift-cluster-csi-drivers

E1007 09:22:39.958324       1 config_yaml.go:208] Unmarshal failed: yaml: unmarshal errors:
  line 1: cannot unmarshal !!seq into config.CommonConfigYAML
I1007 09:22:39.958515       1 config.go:272] ReadConfig INI succeeded. INI-based cloud-config is deprecated and will be removed in 2.0. Please use YAML based cloud-config.
I1007 09:22:39.959600       1 config.go:283] Config initialized
W1007 09:22:39.959738       1 vspherecontroller.go:910] vCenter vcenter1.vmware.gsslab.pnq2.redhat.com is missing from vCenter map
E1007 09:22:39.959815       1 runtime.go:79] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
goroutine 731 [running]:
k8s.io/apimachinery/pkg/util/runtime.logPanic({0x2cf0f80, 0x54f9210})
        k8s.io/apimachinery@v0.30.3/pkg/util/runtime/runtime.go:75 +0x85
k8s.io/apimachinery/pkg/util/runtime.HandleCrash({0xc000b0f4e8, 0x1, 0xc001adc000?})
        k8s.io/apimachinery@v0.30.3/pkg/util/runtime/runtime.go:49 +0x6b
panic({0x2cf0f80?, 0x54f9210?})
        runtime/panic.go:770 +0x132

The storage CO goes in panic:

$ oc get co storage
NAME      VERSION   AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
storage   4.17.0    True        False         True       6d21h   VSphereCSIDriverOperatorCRDegraded: VMwareVSphereControllerDegraded: panic caught:...

    The vmware-vsphere-csi-driver-operator should not go into panic even if the configuration is missing or incorrect.