https://github.com/openshift/origin/pull/21721
This is verified on oc v3.11.66 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO Server https://ip-172-18-12-68.ec2.internal:8443 openshift v3.11.66 kubernetes v1.11.0+d4cacc0 1.Create two nfs recyled pv [root@ip-172-18-12-68 ~]# oc get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE nfs-1 5Gi RWX Recycle Available 2m nfs-2 5Gi RWX Recycle Available 2.Create a pvc nfsc-1, and bound to one pv nfs-1 [root@ip-172-18-12-68 ~]# oc get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE nfs-1 5Gi RWX Recycle Bound s4l93/nfsc-1 9m nfs-2 5Gi RWX Recycle Available 10m 3.Create pod nfs-1, using pvc nfsc-1 4.Prepare the pvc yaml file, make the pvc nfs-1 bound to pv nfs-2 { "apiVersion": "v1", "kind": "PersistentVolumeClaim", "metadata": { "name": "nfsc-1" }, "spec": { "volumeName": "nfs-2", "accessModes": [ "ReadWriteMany" ], "resources": { "requests": { "storage": "5Gi" } } } } ~ 5.Re-create pvc nfsc-1 [root@ip-172-18-12-68 ~]# ./test.sh pod "nfs-1" deleted persistentvolumeclaim "nfsc-1" deleted persistentvolumeclaim/nfsc-1 created pod/nfs-1 created 6.Check pv status [root@ip-172-18-12-68 ~]# oc get pv NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE nfs-1 5Gi RWX Recycle Available 12m nfs-2 5Gi RWX Recycle Bound s4l93/nfsc-1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0096