Pod fails with: 'MountVolume.SetUp failed for volume "<volume-name>": stat /<volume-path>/pods/<uuid>/volumes/kubernetes.io/<volume-name>: no such file or directory' in OCP 3.x

Solution Verified - Updated -

Issue

A pod doesn't start and stays with the status ContainerCreating or Error. This can lead to RESTARTS pod status to be greater than 0. Event logs shows the error:

MountVolume.SetUp failed for volume "<volume-name>": stat /var/lib/origin/openshift.local.volumes/pods/<pod-uuid>/volumes/kubernetes.io/<volume-name>: no such file or directory.

Environment

  • Red Hat OpenShift Container Platform (OCP) 3.x

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