Bug 2057001 - ocs-operator does not make sure there is no storageconsumer in the provider cluster when we disable AllowRemoteStorageConsumers
Summary: ocs-operator does not make sure there is no storageconsumer in the provider c...
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
medium
Target Milestone: ---
: ODF 4.10.0
Assignee: Nitin Goyal
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-22 14:23 UTC by Nitin Goyal
Modified: 2023-08-09 17:00 UTC (History)
6 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage ocs-operator pull 1530 0 None Merged ocs to ocs: small general fixes 2022-02-22 14:27:42 UTC
Github red-hat-storage ocs-operator pull 1531 0 None open provider-controller: check StorageConsumers in disable case too 2022-02-22 14:24:59 UTC
Github red-hat-storage ocs-operator pull 1550 0 None open Bug 2057001:[release-4.10] ocs to ocs: small general fixes 2022-02-22 16:57:42 UTC
Github red-hat-storage ocs-operator pull 1551 0 None open Bug 2057001:[release-4.10] provider-controller: check StorageConsumers in disable case too 2022-02-22 16:57:36 UTC

Description Nitin Goyal 2022-02-22 14:23:02 UTC
Description of problem (please be detailed as possible and provide log
snippets):

We have 2 ways to opt-out as a provider
- delete the storageCluster
- disable the AllowRemoteStorageConsumers flag and keep the storagecluster

ocs-operator should make sure that all storage consumers are offBoarded before deleting the provider resources (API Server etc.) in both the cases. But it only does it in the first case.


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)?
Consumers won't be able to offboard later.

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)?
3

Can this issue reproducible?
Yes


Can this issue reproduce from the UI?
Yes

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

Steps to Reproduce:
1. create a odf to odf provider cluster
2. onboard the consumer
3. disable to AllowRemoteStorageConsumers flag in the storagecluster in the provider cluster.


Actual results:
ocs-operator does not check for existing storageConsumer.

Expected results:
ocs-operator should make sure storageConsumer does not exist.


Additional info:

Comment 9 Mudit Agarwal 2022-02-28 12:39:47 UTC
Not sure why this was moved to POST, I don't see a FailedQA also. Moving it back to ON_QA
If this is FailedQA then please justify and move it to ASSIGNED.

Comment 11 Neha Berry 2022-03-10 20:22:52 UTC
Hi Nitin can you confirm if the verification in comment#10 is enough for moving this bug to verified?


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