Bug 1699253

Summary: Default storage class in vsphere does not work
Product: OpenShift Container Platform Reporter: Wenqi He <wehe>
Component: StorageAssignee: Bradley Childs <bchilds>
Status: CLOSED DUPLICATE QA Contact: Liang Xia <lxia>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.1.0CC: aos-bugs, aos-storage-staff, chaoyang, hekumar, mawong, wzheng
Target Milestone: ---Keywords: TestBlocker
Target Release: 4.1.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: 2019-04-12 14:06:02 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:

Description Wenqi He 2019-04-12 08:48:05 UTC
Description of problem:
Default sc in vsphere cannot provision persist volume

Version-Release number of selected component (if applicable):
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.0.0-0.nightly-2019-04-10-182914   True        False         45m     Cluster version is 4.0.0-0.nightly-2019-04-10-182914

How reproducible:
Always

Steps to Reproduce:
1. Set up OCP4 on vsphere
2. Create pvc to use default sc
3. Create the pod to use pvc

Actual results:
Dynamic provision failed
$ oc describe pvc pvc
Name:          pvc
Namespace:     default
StorageClass:  thin
Status:        Pending
Volume:        
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/vsphere-volume
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      
Access Modes:  
VolumeMode:    Filesystem
Events:
  Type       Reason              Age                   From                         Message
  ----       ------              ----                  ----                         -------
  Warning    ProvisioningFailed  2m14s (x12 over 12m)  persistentvolume-controller  Failed to provision volume with StorageClass "thin": Post https://vcsa-ci.vmware.devcluster.openshift.com:443/sdk: x509: certificate signed by unknown authority
Mounted By:  podtest


Expected results:
Dynamic provision works


PVC Dump:
$ oc get pvc -o yaml
apiVersion: v1
items:
- apiVersion: v1
  kind: PersistentVolumeClaim
  metadata:
    annotations:
      volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/vsphere-volume
    creationTimestamp: 2019-04-12T07:57:27Z
    finalizers:
    - kubernetes.io/pvc-protection
    name: pvc
    namespace: default
    resourceVersion: "36415"
    selfLink: /api/v1/namespaces/default/persistentvolumeclaims/pvc
    uid: 9d6bfe5c-5cf8-11e9-be86-0050569b271c
  spec:
    accessModes:
    - ReadWriteOnce
    dataSource: null
    resources:
      requests:
        storage: 1Gi
    storageClassName: thin
    volumeMode: Filesystem
  status:
    phase: Pending
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""


StorageClass Dump (if StorageClass used by PV/PVC):
$ oc get sc -o yaml
apiVersion: v1
items:
- apiVersion: storage.k8s.io/v1
  kind: StorageClass
  metadata:
    annotations:
      storageclass.kubernetes.io/is-default-class: "true"
    creationTimestamp: 2019-04-12T07:11:53Z
    name: thin
    ownerReferences:
    - apiVersion: v1
      kind: clusteroperator
      name: storage
      uid: cfa24e27-5cf0-11e9-b324-0050569bd3fe
    resourceVersion: "10702"
    selfLink: /apis/storage.k8s.io/v1/storageclasses/thin
    uid: 3ff765c7-5cf2-11e9-b1b7-0050569b3bff
  parameters:
    diskformat: thin
  provisioner: kubernetes.io/vsphere-volume
  reclaimPolicy: Delete
  volumeBindingMode: Immediate
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""


Additional info:

Comment 1 Matthew Wong 2019-04-12 14:00:28 UTC
Are there controller-manager logs? If controller-manager can't talk to the cluster at all, it may be a cloudprovider config issue... There should be a cloud-config configmap in namespace openshift-kube-controller-manager, what does that look like?

Comment 2 Hemant Kumar 2019-04-12 14:06:02 UTC
This is a known issue. Please see - https://bugzilla.redhat.com/show_bug.cgi?id=1698180 . It should be fixed in the installer. There is a workaround available (I have documented it in the linked bug).

*** This bug has been marked as a duplicate of bug 1698180 ***