Description of problem: ========================= In provider mode, the ocs-storagecluster-ceph-rbd-virtualization resource is not automatically deployed. This storage class is recommended for virtualization workloads and should be created by default to ensure optimal performance and integration. DF threads with discussions https://ibm-systems-storage.slack.com/archives/C05RJB6H0LQ/p1720717001944549 https://ibm-systems-storage.slack.com/archives/C05RJB6H0LQ/p1720708288135689 Version-Release number of selected component (if applicable): ============================================================== ODF 4.16 and 4.17 and above How reproducible: ================== Always Steps to Reproduce: -================== 1. Create a provider mode cluster from UI which automatically installs the native ocs-storage-client 2. Check for the storageclasses that are created 3. Actual results: ================= ocs-storagecluster-ceph-rbd-virtualization is not created automatically Expected results: =================== ocs-storagecluster-ceph-rbd-virtualization should be created automatically Additional info: ==================== From dev ---------- This storage class is available in internal mode if ODF detect oVrit is installed. But that logic is missing from provider mode. This is not an RFE, this is oversight, which we will treat as a bug fix Github issue by HCI team https://github.ibm.com/ProjectAbell/abell-tracking/issues/39762 Must-gather http://rhsqe-repo.lab.eng.blr.redhat.com/OCS/ocs-qe-bugs/bug-2302047.zip
Collected all the required code changes for default creation of storageclass for virtualization workloads, They are few cases to be discussed and analyzed. Initially triggering the ocs-client-operator to detect the kube-virt crd present in the cluster, Storage class creation has to be triggered through storageclaim for virtualization workloads.