Bug 2009886

Summary: [DR] S3 backend status missing for ODR cluster and hub operators
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Jean-Charles Lopez <jelopez>
Component: odf-drAssignee: Shyamsundar <srangana>
odf-dr sub component: ramen QA Contact: Elad <ebenahar>
Status: CLOSED CANTFIX Docs Contact:
Severity: unspecified    
Priority: unspecified CC: aclewett, ebenahar, jespy, madam, muagarwa, ocs-bugs, odf-bz-bot, olakra, rcyriac, sagrawal, srangana
Version: 4.9   
Target Milestone: ---   
Target Release: ODF 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-18 13:28:36 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 Jean-Charles Lopez 2021-10-01 21:21:49 UTC
Description of problem (please be detailed as possible and provide log
snippests):
When deploying or monitoring the ODR setup on the hub cluster or the managed cluster there is no status field to monitor the health of the S3 backend that have been configured.
This is a problem for deployment automation but also for day 2 operations in order to monitor all clusters can successfully connect t to the configured s3 backend


Version of all relevant components (if applicable):
4.9.0 nightly builds


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

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


Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
No

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


Steps to Reproduce:
1. Deploy ODR cluster and hub operators
2. Search for s3 backend status field is fruitless
3.


Actual results:


Expected results:


Additional info:

Comment 2 Jean-Charles Lopez 2021-10-01 22:18:16 UTC
As a suggestion, may be the only place where it would nicely fit is to have the status located into the DRPolicy CR. This way we can check the status of each DRPolicy as soon as it gets created and can warn if something is wrong before continuing.

Comment 13 Mudit Agarwal 2021-11-17 09:10:04 UTC
Moving it to 4.10 for adding managed cluster side validations

Comment 17 Mudit Agarwal 2022-03-01 14:08:04 UTC
Not a blocker, moving it out of 4.10 because of dev freeze

Comment 20 Mudit Agarwal 2022-06-07 09:39:52 UTC
Are we fixing this in 4.11?

Comment 21 Shyamsundar 2022-06-07 11:23:24 UTC
(In reply to Mudit Agarwal from comment #20)
> Are we fixing this in 4.11?

No, this is not being fixed in 4.11.