Bug 2322458 - Virtualization storage class isn't created upon presence of VirtualMachine CRD
Summary: Virtualization storage class isn't created upon presence of VirtualMachine CRD
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.18
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: Malay Kumar parida
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-10-29 14:46 UTC by Anton Asserzon
Modified: 2024-11-04 07:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2313492 0 unspecified ON_QA [ODF 4.14.z] Creation of virtualmachines.kubevirt.io CRD doesn't trigger a reconcile 2024-11-04 06:21:25 UTC
Red Hat Issue Tracker OCSBZM-9450 0 None None None 2024-10-29 14:47:46 UTC

Description Anton Asserzon 2024-10-29 14:46:32 UTC 
Description of problem:

When a VirtualMachine CRD is present, a new StorageClass needs to be created by ocs-operator: "ocs-storagecluster-ceph-rbd-virtualization"
As of OCS Operator v4.18.0-42.stable, this does not happen anymore

This broke cluster deployment in CNV QE for 4.18 and 4.18-dependent versions, since our CNV deployment jobs require this SC.

The workaround is to run this:
oc -n openshift-storage rollout restart deployment ocs-operator

Can this issue reproduce from the UI?
Yes, deploy ODF, deploy CNV, check StorageClasses

Steps to Reproduce:
Deploy ODF, Deploy CNV, oc get storageclass

Actual results:
ocs-storagecluster-ceph-rbd-virtualization SC is not listed

Expected results:
ocs-storagecluster-ceph-rbd-virtualization SC exists
Comment 2 Anton Asserzon 2024-10-29 14:51:06 UTC 
For reference
https://github.com/red-hat-storage/ocs-operator/blob/main/controllers/storagecluster/storageclasses.go#L455
Note You need to log in before you can comment on or make changes to this bug.