Bug 1525317

Summary: [vSphere] PV does not provision, no events showing provisioner status
Product: OpenShift Container Platform Reporter: Jianwei Hou <jhou>
Component: StorageAssignee: Bradley Childs <bchilds>
Status: CLOSED NOTABUG QA Contact: Jianwei Hou <jhou>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.8.0CC: aos-bugs, aos-storage-staff, eboyd
Target Milestone: ---   
Target Release: 3.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-21 03:31:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1525357    
Bug Blocks:    

Description Jianwei Hou 2017-12-13 03:13:17 UTC
Description of problem:
vSphere volume does not provision on 3.8. The PVC stuck at pending state.
`oc describe pvc` does not show any events with the provisioning status.
# oc describe pvc pvc
Name:          pvc
Namespace:     jhou
StorageClass:  vspheredefault
Status:        Pending
Volume:        
Labels:        <none>
Annotations:   <none>
Capacity:      
Access Modes:  
Events:        <none>


Version-Release number of selected component (if applicable):
openshift v3.8.18
kubernetes v1.8.1+0d5291c
etcd 3.2.8

How reproducible:
Always

Steps to Reproduce:
1. Configure vSphere cloud provider on the VMs.
2. Create a default StorageClass
3. Create a PVC

Actual results:
3. PV does not get created

Expected results:
3. A PV is automatically provisioned

Master Log:

PVC Dump:
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi

StorageClass Dump (if StorageClass used by PV/PVC):
kind: StorageClass
apiVersion: storage.k8s.io/v1beta1
metadata:
  name: vspheredefault
  annotations:
    storageclass.kubernetes.io/is-default-class: "true"
provisioner: kubernetes.io/vsphere-volume

Additional info:

Comment 1 Erin Boyd 2017-12-13 15:39:25 UTC
Ensure dynamic provisioning is enabled. I've seen this behavior is the past.

Comment 3 Jianwei Hou 2017-12-21 03:31:06 UTC
Redeployed on v3.8.22, not reproducible now. Earlier problem might be caused by some installation issues. Closing.