Bug 2056649 - UpdateCapacity fails because the grpc response does not return any granted capacity
Summary: UpdateCapacity fails because the grpc response does not return any granted ca...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: ocs-operator
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.10.0
Assignee: Santosh Pillai
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-21 17:29 UTC by Santosh Pillai
Modified: 2023-08-09 17:00 UTC (History)
10 users (show)

Fixed In Version: 4.10.0-164
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-21 09:12:47 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage ocs-operator pull 1544 0 None open Return granted capacity in UpdataCapacity grpc response 2022-02-21 17:30:36 UTC
Github red-hat-storage ocs-operator pull 1545 0 None open [release-4.10] Return granted capacity in UpdataCapacity grpc response 2022-02-21 18:46:33 UTC

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


Note You need to log in before you can comment on or make changes to this bug.