Bug 1467575
| Summary: | Add support for azure-file storageclasses | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Eduardo Minguez <eminguez> |
| Component: | Storage | Assignee: | hchen |
| Status: | CLOSED NOTABUG | QA Contact: | Wenqi He <wehe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.5.0 | CC: | aos-bugs, bchilds, jliggitt, jsafrane |
| Target Milestone: | --- | Flags: | eminguez:
needinfo-
|
| Target Release: | 3.7.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-09-07 19:29:27 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: | |||
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. Azure provisioning is not in 3.5, but will be in 3.7+ 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. |
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: