Bug 2211807

Summary:	[RDR] DR dashboard doesn't reflect correct health status of operators on hub cluster when they are unhealthy
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Sidhant Agrawal <sagrawal>
Component:	management-console	Assignee:	gowtham <gshanmug>
Status:	CLOSED ERRATA	QA Contact:	Sidhant Agrawal <sagrawal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.13	CC:	gshanmug, kramdoss, nthomas, odf-bz-bot, skatiyar
Target Milestone:	---
Target Release:	ODF 4.14.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.14.0-110	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-11-08 18:51:19 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 Sidhant Agrawal 2023-06-02 05:01:25 UTC

Created attachment 1968462 [details]
Dashboard when operators pods are not in Running state

Created attachment 1968462 [details]
Dashboard when operators pods are not in Running state

Description of problem (please be detailed as possible and provide log
snippests):
The Operator status card in DR dashboard doesn't reflect correct health status of "Disaster recovery" 
It keeps showing healthy status even when there's an issue with DR hub and MCO operators on hub cluster.

Version of all relevant components (if applicable):
OCP: 4.13.0-0.nightly-2023-05-25-001936
ODF: 4.13.0-206
ceph version 17.2.6-50.el9cp (c202ddb5589554af0ce43432ff07cd7ce8f35243) quincy (stable)
ACM: 2.8.0-183 (acm-custom-registry:2.8.0-DOWNSTREAM-2023-05-25-02-20-00)
Submariner: 0.15.0 (image: brew.registry.redhat.io/rh-osbs/iib:505608)

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

Can this issue reproducible?
always

Can this issue reproduce from the UI?
yes

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


Steps to Reproduce:
1. Deploy RDR setup
2. Enable ACM observability and whitelist DR metrics: https://docs.google.com/document/d/1hl9BOShVpHQKZPXmMZJes3rrQdvy3IHBHmQSfqMSJr8/edit?usp=sharing
3. Bring DR hub and MCO operator pods into Pending state (Make nodes unschedulable and delete the operator pods)
4. Observe the DR dashboard (All Cluster -> Data services -> Data policies -> Overview)
   - No indication if DR hub and MCO operators are in unhealthy state


Actual results:
DR dashboard doesn't reflect correct health status of (DR hub + MCO) operators

Expected results:
DR dashboard should reflect correct health status of (DR hub + MCO) operators when the operators pods are not healthy

Additional info:

Comment 7 Sanjal Katiyar 2023-06-06 09:00:24 UTC

will move back to 4.13.z once we have appropriate flag for that...

Comment 8 Sanjal Katiyar 2023-06-07 05:40:58 UTC

(In reply to Sanjal Katiyar from comment #7)
> will move back to 4.13.z once we have appropriate flag for that...

or create a new one (keeping current BZ for 4.14)

Comment 17 errata-xmlrpc 2023-11-08 18:51:19 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.14.0 security, enhancement & bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6832