Description of problem: We have set up OCP to dynamically create vmdk-files in vSphere as persistant volumes. When creating a pod using persistant volumes, we get this error message: Failed to attach volume "pvc-c60418fb-a1e8-11e7-978a-005056bf7cc7" on node "ocp-prod-node01.x.y " with: datastore 'D6OCPV01' not found When we specified "datastore: OCPPROD/D6OCPV01" it where able to provision the volume, but not mount it. ## Failed to attach volume "pvc-ec2816b1-a2c4-11e7-978a-005056bf7cc7" on node "ocp-prod-node02.local.husbanken.no" with: datastore 'D6OCPV01' not found" Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: It is not able to locate the datastore. Expected results: It shpuld be able to locate it Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
It's hard to guess what's wrong without reproducing the bug locally. @Jianwei, can you or someone from your team try to reproduce the bug on our systems and give me access there? I suspect that it's caused by https://github.com/kubernetes/kubernetes/issues/44007 and it's fixed by https://github.com/kubernetes/kubernetes/pull/44868, but that's just a wild guess.
The PR is not merged yet
Tested on v3.6.173.0.63 Volume mounted successfully when storageclass has 'datastore' parameter.
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/RHSA-2017:3389