Description of problem: Dynamic provision pvc is pending , no pv is created Version-Release number of selected component (if applicable): oc v3.1.1.910 kubernetes v1.2.0-alpha.7-703-gbc4550d Docker 1.8.2-el7, build a01dc02/1.8.2 kernel 3.10.0-327.10.1.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a pvc using below json file { "kind": "PersistentVolumeClaim", "apiVersion": "v1", "metadata": { "name": "claim2", "annotations": { "volume.alpha.kubernetes.io/storage-class": "foo" } }, "spec": { "accessModes": [ "ReadWriteOnce" ], "resources": { "requests": { "storage": "3Gi" } } } } 2. Check PVC status apiVersion: v1 kind: PersistentVolumeClaim metadata: annotations: volume.alpha.kubernetes.io/storage-class: foo volume.experimental.kubernetes.io/provisioning-required: volume.experimental.kubernetes.io/provisioning-completed creationTimestamp: 2016-03-17T02:39:50Z name: claim2 namespace: chao resourceVersion: "934987" selfLink: /api/v1/namespaces/chao/persistentvolumeclaims/claim2 uid: 85be6a47-ebe9-11e5-9fd3-0a40e3e0a381 spec: accessModes: - ReadWriteOnce resources: requests: storage: 3Gi status: phase: Pending Actual results: PVC is pending, no pv is created Expected results: PVC should bind to pv Additional info: - apiVersion: v1 kind: PersistentVolume metadata: annotations: kubernetes.io/createdby: aws-ebs-dynamic-provisioner volume.alpha.kubernetes.io/storage-class: foo volume.experimental.kubernetes.io/provisioning-required: "true" creationTimestamp: 2016-03-17T02:39:50Z generateName: pv-aws- name: pv-aws-4ykny resourceVersion: "959316" selfLink: /api/v1/persistentvolumes/pv-aws-4ykny uid: 85c07e28-ebe9-11e5-90a5-0aadb0f8cf89 spec: accessModes: - ReadWriteOnce awsElasticBlockStore: fsType: ext4 volumeID: dummy capacity: storage: 3Gi claimRef: apiVersion: v1 kind: PersistentVolumeClaim name: claim2 namespace: chao resourceVersion: "934985" uid: 85be6a47-ebe9-11e5-9fd3-0a40e3e0a381 persistentVolumeReclaimPolicy: Delete status: message: "UnauthorizedOperation: You are not authorized to perform this operation.\n\tstatus code: 403, request id: " phase: Failed
I am assuming this is correctly filed for OpenShift Online. If not, this needs to be against the Storage component of "OpenShift Origin". For Online, we do not enable/configure dynamic provisioning of PVs. Ops is responsible for ensuring that PVs are available. Additionally, all PVs are created of size 1G each. So, in the above example, a 3G PVC will not be able to successfully bind to an existing PV.
Verified due to https://bugzilla.redhat.com/show_bug.cgi?id=1318519#c1