Bug 1467575 - Add support for azure-file storageclasses
Summary: Add support for azure-file storageclasses
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.7.0
Assignee: hchen
QA Contact: Wenqi He
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-04 09:03 UTC by Eduardo Minguez
Modified: 2020-06-04 12:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-07 19:29:27 UTC
Target Upstream Version:
Embargoed:
eminguez: needinfo-


Attachments (Terms of Use)

Description Eduardo Minguez 2017-07-04 09:03:53 UTC
Description of problem:
Azure-file is supported but cannot be used as storageclass

Version-Release number of selected component (if applicable):
v3.5.5.26

How reproducible:
Deploy a fresh cluster in Azure and try to create a storageclass with azure-file (azure-disk works)

Steps to Reproduce:
1. Create a storageclass as:

kind: StorageClass
apiVersion: storage.k8s.io/v1beta1
metadata:
  name: generic
  annotations:
    storageclass.beta.kubernetes.io/is-default-class: "true"
provisioner: kubernetes.io/azure-file
parameters:
  storageAccount: sapv1emingueztst

2. Create a pvc as:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: prueba
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi

3. oc describe pvc prueba says:
...
Events:
  FirstSeen	LastSeen	Count	From				SubObjectPath	Type		Reason		Message
  ---------	--------	-----	----				-------------	--------	------		-------
  14m		1s		60	{persistentvolume-controller }			Warning		ProvisioningFailed	no volume plugin matched

Actual results:
no volume created and "no volume plugin matched" error

Expected results:
volume created, bounded and working

Additional info:
I think this is the k8s pr that implements this: https://github.com/kubernetes/kubernetes/pull/42170
Also, beware requirements for installation: https://access.redhat.com/solutions/2844731
And update documentation on how to create a storageclass of azure-file kind.

Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 1 Jan Safranek 2017-07-04 12:46:46 UTC
AFAIK, dynamic provisioning of azure-file is part of Kubernetes 1.7, i.e. will appear in OpenShift 3.7.

Assigning to Huamin to confirm + estimate how hard would it be to port it back to 3.5 / 3.6.  Then we can decide if it's worth the effort.

Comment 5 Bradley Childs 2017-09-07 19:29:27 UTC
Azure provisioning is not in 3.5, but will be in 3.7+

Comment 6 Eduardo Minguez 2017-09-08 06:50:46 UTC
Actually, Azure file is documented in 3.5 docs https://docs.openshift.com/container-platform/3.5/install_config/persistent_storage/persistent_storage_azure_file.html

Shall I open a doc BZ for removing that chapter for 3.5?

Thanks.


Note You need to log in before you can comment on or make changes to this bug.