-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The customer is receiving the `PodStartupStorageOperationsFailing` alert:
~~~
description = Failing storage operation "volume_attach" of volume plugin kubernetes.io/csi:csi.vsphere.vmware.com was preventing Pods on node from starting for past 5 minutes. Please investigate Pods that are "ContainerCreating" on the node: "oc get pod --field-selector=spec.nodeName= --all-namespaces | grep ContainerCreating". Events of the Pods should contain exact error message: "oc describe pod -n <pod namespace> <pod name>".
summary = Pods can't start because volume_attach of volume plugin kubernetes.io/csi:csi.vsphere.vmware.com is permanently failing on node
~~~
However, when we checked for any pods in the ContainerCreating state within the cluster, none were found in that state.
Additionally, to further troubleshoot the issue, we attempted to identify the node name in order to collect the sos report. However, the node name is not displayed in the alert within the OCP web console.