Bug 2079663

Summary: change default image features in RBD storageclass
Product: OpenShift Container Platform Reporter: Divyansh Kamboj <dkamboj>
Component: Console Storage PluginAssignee: Divyansh Kamboj <dkamboj>
Status: CLOSED ERRATA QA Contact: Shrivaibavi Raghaventhiran <sraghave>
Severity: low Docs Contact:
Priority: low    
Version: 4.11CC: badhikar, jefbrown, mkarnik, nthomas, tdesala, ykaul
Target Milestone: ---   
Target Release: 4.11.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: 2022-08-10 11:09:16 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:

Description Divyansh Kamboj 2022-04-28 03:46:01 UTC
In UI for the RBD storageclass, the image features are set to default as layering, As we are changing the default image features in ODF RBD storageclass, the same changes need to be reflected in the UI also. More details about the New storageclass is here https://issues.redhat.com/browse/RHSTOR-2502

Comment 5 Shrivaibavi Raghaventhiran 2022-07-25 15:13:55 UTC
Test Version:
-------------
OCP - 4.11.0-0.nightly-2022-07-13-131410
ODF - quay.io/rhceph-dev/ocs-registry:4.11.0-113

Test Steps:
------------
1. Created SC "samplestorageclass" via UI with RBD provisioner "openshift-storage.rbd.csi.ceph.com"
2. Created PVC (RBD RWO) with above created SC and attached a pod

Observations:
--------------
* RBD SC had following imageFeatures 

imageFeatures: layering,deep-flatten,exclusive-lock,object-map,fast-diff

Console Output:
-----------------

$ oc get pod,pvc -n namespace-fxyr
NAME                               READY   STATUS      RESTARTS   AGE
pod/fedorapod-ddbeiftbg-1-deploy   0/1     Completed   0          2m4s
pod/fedorapod-ddbeiftbg-1-wtzmz    1/1     Running     0          113s

NAME                                  STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS         AGE
persistentvolumeclaim/pvc-jacccopto   Bound    pvc-af370635-8f64-4eb3-a7b8-edb8ca7cad1e   500Gi      RWO            samplestorageclass   3m17s

$ oc get sc samplestorageclass -o yaml
allowVolumeExpansion: true
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  creationTimestamp: "2022-07-25T14:51:59Z"
  name: samplestorageclass
  resourceVersion: "15753515"
  uid: 3a0952f5-89ef-47ad-8130-1209e26af888
parameters:
  clusterID: openshift-storage
  csi.storage.k8s.io/controller-expand-secret-name: rook-csi-rbd-provisioner
  csi.storage.k8s.io/controller-expand-secret-namespace: openshift-storage
  csi.storage.k8s.io/fstype: ext4
  csi.storage.k8s.io/node-stage-secret-name: rook-csi-rbd-node
  csi.storage.k8s.io/node-stage-secret-namespace: openshift-storage
  csi.storage.k8s.io/provisioner-secret-name: rook-csi-rbd-provisioner
  csi.storage.k8s.io/provisioner-secret-namespace: openshift-storage
  fsName: ocs-storagecluster-cephfilesystem
  imageFeatures: layering,deep-flatten,exclusive-lock,object-map,fast-diff
  imageFormat: "2"
  pool: ocs-storagecluster-cephblockpool
provisioner: openshift-storage.rbd.csi.ceph.com
reclaimPolicy: Delete
volumeBindingMode: WaitForFirstConsumer


With all the above observations moving the BZ to verified state

Comment 6 errata-xmlrpc 2022-08-10 11:09:16 UTC
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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069