Bug 2056649

Summary:	UpdateCapacity fails because the grpc response does not return any granted capacity
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Santosh Pillai <sapillai>
Component:	ocs-operator	Assignee:	Santosh Pillai <sapillai>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Neha Berry <nberry>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.10	CC:	madam, muagarwa, nberry, ocs-bugs, odf-bz-bot, omitrani, rperiyas, sabose, sgatfane, sostapov
Target Milestone:	---
Target Release:	ODF 4.10.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.10.0-164	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-21 09:12:47 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-21 17:29:32 UTC

Description of problem (please be detailed as possible and provide log
snippests):

After UpdateCapacity grpc call, the controller on the consumer side uses the `granted capacity` value to update the storagecluster status. This operation fails if `granted capacity` is not returned from this call in case of a success.

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?


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


Can this issue reproducible?


Can this issue reproduce from the UI?


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


Steps to Reproduce:
1.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 4 suchita 2022-03-03 13:57:57 UTC

For verification this bug, Please share the detailed steps.

Comment 5 Santosh Pillai 2022-03-04 06:55:09 UTC

Verification steps:
1. Update the requested capacity in the StorageCluster on the consumer side.
2. Verify that requested capacity the StorageConsumer cluster CR spec on the Provider cluster is updated