Hide Forgot
Description of problem: pvc can be not bounded to a pv Version-Release number of selected component (if applicable): Server https://api.dev-preview-stg.openshift.com openshift v3.3.1.4 kubernetes v1.3.0+52492b4 How reproducible: always Steps to Reproduce: 1. Login the web console with a normal user 2. Create a new project and select the Storage to choose "request storage" 3. Full fill the name and select a random accessmode with capacity 1GiB 4. Check the pvc status Actual results: pvc is in pending status: [root@ymsun online-test]# oc get pvc testpvc NAME STATUS VOLUME CAPACITY ACCESSMODES AGE testpvc Pending 3m Expected results: 4. pvc is bounded to a pv Additional info:
Checked with Ops team: 1. In master-config.yaml, dynamicProvisioningEnabled is set to "false" 2. online-volume-provisioner pod is not started. Ops team member zhiwliu can not find the dc for this pod.
Since we are no longer using the provisioner pod in Online environments, the dc has been removed. We're using manually-provisioned PVs in Online until 3.4 is released. I have provisioned some PVs for dev-preview-stg, so this issue should be resolved now.
Testing on dev-preview-stg: 1. request a storage with RWO accessmode: yasun-test-3 Bound to volume pv-1-dev-preview-stg-master-defb2-vol-2ed248bf 1 GiB RWO (Read-Write-Once) a few seconds 2. request a storage with RWX accessmode: yasun-test-2 Pending - RWX (Read-Write-Many) 5 minutes 3. request a storage with ROX accessmode: yasun-test-1 Pending - ROX (Read-Only-Many) 4 minutes @Stefanie Forrester, About the pending issue in step 2 and step 3, I think it has been mentioned in the bug: https://bugzilla.redhat.com/show_bug.cgi?id=1401356 . And I assume that PVs you have created on dev-preview-stg are all in RWO accessmode, am I correct?