Bug 2055691

Summary: StorageConsumer: update capacity only if requested and granted capacity are different
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Santosh Pillai <sapillai>
Component: ocs-operatorAssignee: Santosh Pillai <sapillai>
Status: CLOSED CURRENTRELEASE QA Contact: Neha Berry <nberry>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.10CC: madam, muagarwa, nberry, ocs-bugs, odf-bz-bot, rperiyas, sgatfane, sostapov
Target Milestone: ---   
Target Release: ODF 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.10.0-163 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-21 09:12:46 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 Santosh Pillai 2022-02-17 14:29:12 UTC
Description of problem (please be detailed as possible and provide log
snippests):

UpdateCapacity grpc call is invoked even if the RequestedCapacity and GrantedCapacity are same. 


Version of all relevant components (if applicable):


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?


Is there any workaround available to the best of your knowledge?
No

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
N/A

If this is a regression, please provide more details to justify this:
No

Steps to Reproduce:
1. Create a Storage Consumer Cluster with Requested capacity and other details.
2. Observe the reconciliation 



Actual results:UpdateCapacity grpc call is invoked even if the RequestedCapacity and GrantedCapacity are same. 


Expected results: Only call UpdateCapacity GRPC call when Requested and Granted Capacity are different.


Additional info:

Comment 5 suchita 2022-03-03 13:57:16 UTC
For verification this bug, Please share the detailed steps.