Closed rgomezceis closed 1 month ago
Is this a BUG REPORT or FEATURE REQUEST?:
Uncomment only one, leave it on its own line: /kind bug /kind feature
Uncomment only one, leave it on its own line:
/kind bug /kind feature
What happened: Pods are in CrashLoopBackOff / Error state.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible): Deploy
Anything else we need to know?:
kubectl logs -n vmware-system-csi vsphere-csi-controller-6598c7f569-8fq7l Defaulted container "csi-attacher" out of: csi-attacher, csi-resizer, vsphere-csi-controller, liveness-probe, vsphere-syncer, csi-provisioner, csi-snapshotter I0719 08:51:50.319116 1 main.go:97] Version: v4.5.1 W0719 08:52:00.321844 1 connection.go:234] Still connecting to unix:///csi/csi.sock W0719 08:52:10.321826 1 connection.go:234] Still connecting to unix:///csi/csi.sock W0719 08:52:20.322532 1 connection.go:234] Still connecting to unix:///csi/csi.sock E0719 08:52:20.325769 1 main.go:136] context deadline exceeded
kubectl logs vsphere-csi-node-r649b -n vmware-system-csi Defaulted container "node-driver-registrar" out of: node-driver-registrar, vsphere-csi-node, liveness-probe I0719 08:47:21.087425 1 main.go:135] Version: v2.10.1 I0719 08:47:21.087466 1 main.go:136] Running node-driver-registrar in mode= I0719 08:47:21.087473 1 main.go:157] Attempting to open a gRPC connection with: "/csi/csi.sock" I0719 08:47:21.087488 1 connection.go:215] Connecting to unix:///csi/csi.sock I0719 08:47:21.088153 1 main.go:164] Calling CSI driver to discover driver name I0719 08:47:21.088164 1 connection.go:244] GRPC call: /csi.v1.Identity/GetPluginInfo I0719 08:47:21.088167 1 connection.go:245] GRPC request: {} I0719 08:47:21.090232 1 connection.go:251] GRPC response: {"name":"csi.vsphere.vmware.com","vendor_version":"v3.3.1"} I0719 08:47:21.090242 1 connection.go:252] GRPC error: <nil> I0719 08:47:21.090247 1 main.go:173] CSI driver name: "csi.vsphere.vmware.com" I0719 08:47:21.090278 1 node_register.go:55] Starting Registration Server at: /registration/csi.vsphere.vmware.com-reg.sock I0719 08:47:21.090403 1 node_register.go:64] Registration Server started at: /registration/csi.vsphere.vmware.com-reg.sock I0719 08:47:21.090537 1 node_register.go:88] Skipping HTTP server because endpoint is set to: "" I0719 08:47:22.525666 1 main.go:90] Received GetInfo call: &InfoRequest{} I0719 08:47:22.533799 1 main.go:101] Received NotifyRegistrationStatus call: &RegistrationStatus{PluginRegistered:false,Error:RegisterPlugin error -- plugin registration failed with err: rpc error: code = Internal desc = failed to get CsiNodeTopology for the node: "ceis-control-plane-3". Error: no matches for kind "CSINodeTopology" in version "cns.vmware.com/v1alpha1",} E0719 08:47:22.533874 1 main.go:103] Registration process failed with error: RegisterPlugin error -- plugin registration failed with err: rpc error: code = Internal desc = failed to get CsiNodeTopology for the node: "ceis-control-plane-3". Error: no matches for kind "CSINodeTopology" in version "cns.vmware.com/v1alpha1", restarting registration container.
Environment:
uname -a
Just DNS problem, my bad.
Is this a BUG REPORT or FEATURE REQUEST?:
What happened: Pods are in CrashLoopBackOff / Error state.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible): Deploy
Anything else we need to know?:
Environment:
uname -a
):