Unable to mount NFS persistent volume after updating to OpenShift Container Platform 3.10.72
Issue
- After upgrade to OpenShift Container Platform 3.10, I noticed all NFS Persistent Volumes cannot be mounted during pod startup, with the following error:
Dec 06 11:19:54 node5.example.net atomic-openshift-node[21705]: I1206 11:19:54.606296 21717 reconciler.go:252] operationExecutor.MountVolume started for volume "example-pv" (UniqueName: "kubernetes.io/nfs/52f4d86d-f93f-11e8-94a6-0050569df267-example-pv") pod "example-db-7d595fc8fb-nf2w5" (UID: "52f4d86d-f93f-11e8-94a6-0050569df267")
Dec 06 11:19:54 node5.example.net atomic-openshift-node[21705]: I1206 11:19:54.608059 21717 nsenter.go:151] failed to resolve symbolic links on /var/lib/origin/openshift.local.volumes/pods/52f4d86d-f93f-11e8-94a6-0050569df267/volumes/kubernetes.io~nfs/example-pv: exit status 1
Dec 06 11:19:54 node5.example.net atomic-openshift-node[21705]: E1206 11:19:54.608142 21717 nestedpendingoperations.go:267] Operation for "\"kubernetes.io/nfs/52f4d86d-f93f-11e8-94a6-0050569df267-example-pv\" (\"52f4d86d-f93f-11e8-94a6-0050569df267\")" failed. No retries permitted until 2018-12-06 11:21:56.608117627 +0100 CET m=+1159.964741283 (durationBeforeRetry 2m2s). Error: "MountVolume.SetUp failed for volume \"example-pv\" (UniqueName: \"kubernetes.io/nfs/52f4d86d-f93f-11e8-94a6-0050569df267-example-pv\") pod \"example-db-7d595fc8fb-nf2w5\" (UID: \"52f4d86d-f93f-11e8-94a6-0050569df267\") : exit status 1"
Environment
- OpenShift Container Platform 3.10.72
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.