Bug 1872549
| Summary: | CSO status of oVirt cluster looks a little of confusion: "DefaultStorageClassControllerAvailable: No default StorageClass for this platform" | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Qin Ping <piqin> |
| Component: | Storage | Assignee: | Christian Huffman <chuffman> |
| Storage sub component: | Operators | QA Contact: | Qin Ping <piqin> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | low | ||
| Priority: | low | CC: | aos-bugs, chuffman, gdeolive |
| Version: | 4.6 | Keywords: | UpcomingSprint |
| Target Milestone: | --- | ||
| Target Release: | 4.6.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: | 2020-10-27 16:33:36 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: | |||
I tested this on an AWS cluster (disabling SC creation here), and confirmed that we're updating the Available condition's message to be a bit more explicit. A PR [1] has been submitted to merge these changes, which should resolve them in oVirt as well. [1] https://github.com/openshift/cluster-storage-operator/pull/85 Verified with: 4.6.0-0.nightly-2020-09-12-164537 "message": "DefaultStorageClassControllerAvailable: StorageClass provided by supplied CSI Driver instead of the cluster-storage-operator". 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 (OpenShift Container Platform 4.6 GA Images), 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:4196 |
Description of problem: In the oVirt cluster, cluster storage operator will not create storage class directly, so from this point, the stauts reports "DefaultStorageClassControllerAvailable: No default StorageClass for this platform" is correct, but the oVirt csi operator managed by CSO will create a default storage class, it makes this status looks a little of confusion. Version-Release number of selected component (if applicable): 4.6.0-0.nightly-2020-08-26-010422 How reproducible: Always Steps to Reproduce: 1.Have an OCP46 cluster on oVirt 2.Check the CSO status 3.Check the storage class Actual results: $ oc get co storage -ojson |jq .status { "conditions": [ { "lastTransitionTime": "2020-08-26T01:40:46Z", "reason": "AsExpected", "status": "False", "type": "Degraded" }, { "lastTransitionTime": "2020-08-26T01:55:37Z", "reason": "AsExpected", "status": "False", "type": "Progressing" }, { "lastTransitionTime": "2020-08-26T01:55:37Z", "message": "DefaultStorageClassControllerAvailable: No default StorageClass for this platform", "reason": "AsExpected", "status": "True", "type": "Available" }, ... $ oc get sc NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE ovirt-csi-sc (default) csi.ovirt.org Delete Immediate false 85m Expected results: Master Log: Node Log (of failed PODs): PV Dump: PVC Dump: StorageClass Dump (if StorageClass used by PV/PVC): Additional info: