Bug 2029413

Summary: [DR] Dummy image size is same as the size of image for which it was created
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Sidhant Agrawal <sagrawal>
Component: csi-driverAssignee: Madhu Rajanna <mrajanna>
Status: CLOSED ERRATA QA Contact: Sidhant Agrawal <sagrawal>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.9CC: jespy, kseeger, madam, mmuench, mrajanna, muagarwa, nberry, ocs-bugs, odf-bz-bot
Target Milestone: ---   
Target Release: ODF 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.10.0-113 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2030742 (view as bug list) Environment:
Last Closed: 2022-04-13 18:50:37 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:
Bug Depends On:    
Bug Blocks: 2030742    

Description Sidhant Agrawal 2021-12-06 12:57:29 UTC 
Description of problem:

This is the related to workaround introduced for bug 2024792, 2019161 which includes creation of dummy image in the cluster.
When creating the dummy image, it uses the size of the image for which it's being created for and therefore the size is larger than the expected value (1MB)

For eg., In a cluster where sample application size is of 5 GiB, dummy image size is also 5 GiB
```
$ rbd ls -l -p ocs-storagecluster-cephblockpool
NAME                                                SIZE    PARENT  FMT  PROT  LOCK
csi-vol-4c734cd8-567e-11ec-9afd-0a580a830025         5 GiB            2            
csi-vol-81cd1c86-5672-11ec-88d6-0a580a800223        50 GiB            2            
csi-vol-dummy-e3b935a9-4f4c-4e29-8743-d8f592228878   5 GiB            2     

$ rbd du -p ocs-storagecluster-cephblockpool
...
NAME                                                PROVISIONED  USED   
csi-vol-4c734cd8-567e-11ec-9afd-0a580a830025              5 GiB  108 MiB
csi-vol-81cd1c86-5672-11ec-88d6-0a580a800223             50 GiB  312 MiB
csi-vol-dummy-e3b935a9-4f4c-4e29-8743-d8f592228878        5 GiB      0 B

```

Output from another cluster where workload consists of multiple PVC of different sizes, the dummy image was created with size of "450 GiB"

```
$ rbd ls -l -p ocs-storagecluster-cephblockpool
NAME                                                SIZE     PARENT  FMT  PROT  LOCK
csi-vol-9712d614-4d1f-11ec-89aa-0a580a830019        200 GiB            2            
csi-vol-9712dd10-4d1f-11ec-89aa-0a580a830019          5 GiB            2            
csi-vol-9714434d-4d1f-11ec-89aa-0a580a830019         30 GiB            2            
csi-vol-9714b3fe-4d1f-11ec-89aa-0a580a830019         15 GiB            2            
csi-vol-9714b5f8-4d1f-11ec-89aa-0a580a830019         50 GiB            2            
csi-vol-9714cc35-4d1f-11ec-89aa-0a580a830019        450 GiB            2            
csi-vol-97168da6-4d1f-11ec-89aa-0a580a830019        100 GiB            2            
csi-vol-c70f19a0-4d13-11ec-b032-0a580a800248         50 GiB            2            
csi-vol-dummy-4ae02941-2531-4d1a-b1d8-0862a4f32385  450 GiB            2 

```

Version-Release number of selected component (if applicable):
ODF: 4.9.0-249.ci

How reproducible:
Always

Steps to Reproduce:
1. Configure ODF for Regional DR
2. Deploy a sample  busybox application
3. Check the size of dummy image using rbd command
rbd ls -l -p ocs-storagecluster-cephblockpool

Actual results:
Dummy image size is same as the size of the image for which it was created

Expected results:
Dummy image size should be smaller irrespective of the size of image created by application

Additional info:
Comment 9 errata-xmlrpc 2022-04-13 18:50:37 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: Red Hat OpenShift Data Foundation 4.10.0 enhancement, security & bug fix 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:1372