Description of problem: FSType is empty when using cinder default storageclass to create a pv Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-04-18-184707 How reproducible: Always Steps to Reproduce: 1.Create a dynamic pv with default storageclass 2.oc describe pv oc describe pv pvc-7fb50215-9276-4c64-8f0a-d63de849f602 Name: pvc-7fb50215-9276-4c64-8f0a-d63de849f602 Labels: failure-domain.beta.kubernetes.io/region= failure-domain.beta.kubernetes.io/zone=nova Annotations: kubernetes.io/createdby: cinder-dynamic-provisioner pv.kubernetes.io/bound-by-controller: yes pv.kubernetes.io/provisioned-by: kubernetes.io/cinder Finalizers: [kubernetes.io/pv-protection] StorageClass: standard Status: Bound Claim: test/pvc1 Reclaim Policy: Delete Access Modes: RWO VolumeMode: Filesystem Capacity: 1Gi Node Affinity: Required Terms: Term 0: failure-domain.beta.kubernetes.io/zone in [nova] Message: Source: Type: Cinder (a Persistent Disk resource in OpenStack) VolumeID: ece31599-6eac-43fb-96a2-cdeecc1f8996 FSType: ReadOnly: false SecretRef: nil Events: <none> 3.FSType is empty Actual results: FSType is empty Expected results: FSType is ext4 Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info:
Is this an actual issue? From the API types: // Filesystem type to mount. // Must be a filesystem type supported by the host operating system. // Ex. "ext4", "xfs", "ntfs". Implicitly inferred to be "ext4" if unspecified. // +optional FSType string If this is unspecified, then it is inferred to be ext4.
It is not an actual issue. so I set the priority is low. We can update it in our code or docs
Commit has been merged upstream, submitting https://github.com/openshift/origin/pull/24990 to include this in origin.
Verification is passed on 4.5.0-0.ci-2020-05-25-012555 oc describe pv Name: pvc-eb6f433b-7ec2-427b-8700-76500d76a777 Labels: failure-domain.beta.kubernetes.io/region=regionOne failure-domain.beta.kubernetes.io/zone=nova Annotations: kubernetes.io/createdby: cinder-dynamic-provisioner pv.kubernetes.io/bound-by-controller: yes pv.kubernetes.io/provisioned-by: kubernetes.io/cinder Finalizers: [kubernetes.io/pv-protection] StorageClass: standard Status: Bound Claim: default/pvc1 Reclaim Policy: Delete Access Modes: RWO VolumeMode: Filesystem Capacity: 1Gi Node Affinity: Required Terms: Term 0: failure-domain.beta.kubernetes.io/zone in [nova] failure-domain.beta.kubernetes.io/region in [regionOne] Message: Source: Type: Cinder (a Persistent Disk resource in OpenStack) VolumeID: a474841c-5958-4dd6-8827-a81757c371fa FSType: ext4 ReadOnly: false SecretRef: nil Events: <none>
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/RHBA-2020:2409