Bug 1689762
| Summary: | The storageClassName is "" in pvc when storageclass is not in CLO | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Anping Li <anli> |
| Component: | Logging | Assignee: | ewolinet |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.1.0 | CC: | aos-bugs, rmeggins |
| Target Milestone: | --- | ||
| Target Release: | 4.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-06-04 10:46:01 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: | |||
If you do not have a storageClassName there it should be interpreted that you want to use an emptydir volume with that size. We aren't correctly evaluating that it is empty. We need to be able to evaluate "" differently from not provided per the k8s docs [1]. [1] https://kubernetes.io/docs/concepts/storage/persistent-volumes/#class-1 Verified and pass on quay.io/openshift/origin-cluster-logging-operator:latest 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-2019:0758 |
Description of problem: If the storage size is specified and storageClassName is not set. the clusterlogging operator generate the pvc resource file using storageClassName: "". that cause the pvc couldn't be bind as there isn't storageClassName "". If we want to use default storage class, Remove the storageclass from the PVC resource file. if we want to use storageClassName as mandatory. We need to update the document. Version-Release number of selected component (if applicable): clusterlogging operator v4.x How reproducible: Always Steps to Reproduce: 1. provide logging CLO Resource without storageclass options. apiVersion: "logging.openshift.io/v1alpha1" kind: "ClusterLogging" metadata: name: "nostorageclassname" spec: managementState: "Managed" logStore: type: "elasticsearch" elasticsearch: nodeCount: 3 resources: limits: memory: 2Gi requests: cpu: 200m memory: 2Gi storage: size: "20G" redundancyPolicy: "SingleRedundancy" visualization: type: "kibana" kibana: replicas: 1 curation: type: "curator" curator: schedule: "*/10 * * * *" collection: logs: type: "fluentd" fluentd: {} 2. Check the pvc status oc get pvc oc edit pvc Actual results: The pvc could't be binding as the storageclass name is "". apiVersion: v1 kind: PersistentVolumeClaim metadata: creationTimestamp: 2019-03-18T02:37:36Z finalizers: - kubernetes.io/pvc-protection name: elasticsearch-elasticsearch-clientdatamaster-0-3 namespace: openshift-logging resourceVersion: "27499" selfLink: /api/v1/namespaces/openshift-logging/persistentvolumeclaims/elasticsearch-elasticsearch-clientdatamaster-0-3 uid: ca5f2068-4926-11e9-b285-0a3cd40e33ca spec: accessModes: - ReadWriteOnce dataSource: null resources: requests: storage: 20G storageClassName: "" status: phase: Pending Expected results: A) Remove the storageclass option from pvc. so the pvc can use the default storageclass. B) indicate storageclass is a mandatory variable